Separate vault-sidecar from consul role
Opened this issue · 0 comments
aurelienmaury commented
The tasks/common/_consul_masters.yml
installs a vault-sidecar envoy proxy to integrate Vault nodes into Consul Service Mesh.
Master Consul nodes are not required to have Vault service on the same host, therefore, this should be either an opt-in installation for this role, or a cleanly separated role.
Create a new role vault_sidecar
with these tasks in it and cut the tasks/common/_consul_masters.yml
from consul role.
Playbooks implied in the demonstrator on scaleway will be impacted, add the new role in the playbooks to maintain service installed.