Storing the Snapshot Agent Config in Vault
This topic describes how to configure the Consul Helm chart to use a snapshot agent config stored in Vault.
Overview
To use an ACL replication token stored in Vault, follow the steps outlined in the Data Integration section.
Complete the following steps once:
- Store the secret in Vault.
- Create a Vault policy that authorizes the desired level of access to the secret.
Repeat the following steps for each datacenter in the cluster:
- Create Vault Kubernetes auth roles that link the policy to each Consul on Kubernetes service account that requires access.
- Update the Consul on Kubernetes helm chart.
Prerequisites
Before you set up data integration between Vault and Consul on Kubernetes, complete the following prerequisites:
- Read and completed the steps in the Systems Integration section of Vault as a Secrets Backend.
- Read the Data Integration Overview section of Vault as a Secrets Backend.
Store the Secret in Vault
First, store the snapshot agent config in Vault:
Create Vault policy
Next, you will need to create a policy that allows read access to this secret.
The path to the secret referenced in the path
resource is the same values that you will configure in the client.snapshotAgent.configSecret.secretName
Helm configuration (refer to Update Consul on Kubernetes Helm chart).
Apply the Vault policy by issuing the vault policy write
CLI command:
Create Vault Authorization Roles for Consul
Next, add this policy to your Consul server Kubernetes auth role:
Note that if you have other policies associated with the Consul server service account that are not in the example, you need to include those as well.
To find out the service account name of the Consul snapshot agent,
you can run the following helm template
command with your Consul on Kubernetes values file:
Update Consul on Kubernetes Helm chart
Now that you have configured Vault, you can configure the Consul Helm chart to use the snapshot agent configuration in Vault:
Note that client.snapshotAgent.configSecret.secretName
is the path of the secret in Vault.
This should be the same path as the one you included in your Vault policy.
client.snapshotAgent.configSecret.secretKey
is the key inside the secret data. This should be the same
as the key you passed when creating the snapshot agent config secret in Vault.