unkin-agent
8e2595c1a9
The certmanager and sshsigner approles are bound to the six legacy VM puppet-master IPs, so the HPA-autoscaled k8s compilers cannot log in and every catalog compile that issues a cert or signs a host key fails. - Add k8s auth roles puppet_certmanager and puppet_sshsigner on k8s/au/syd1, bound to the default service account in namespace puppet - Attach the existing pki_int/pki certmanager and sshca signing policies to them, matching the approle token TTLs - Leave the approle roles and their CIDR bindings untouched
terraform-vault
A repository to manage the configuration of Vault secret engines, authentication modes and policies.
Usage
- Initialize Terraform
Once you have your backend block configured, you need to initialize your Terraform working directory to configure the backend:
terraform init
This command initializes the backend and checks the connection to Consul. If everything is set up correctly, Terraform will start using Consul as its backend for storing the state.
- Common terraform init Errors
If you encounter errors while running terraform init, check the following:
Consul server is reachable: Make sure that the address is correct and that you can connect to the Consul server.
Consul token (if using ACLs): Verify that the token has the correct permissions to write to the specified path in the Consul KV store.
- Example Consul KV Structure
In Consul, the state file will be stored in the KV store under the specified path:
terraform/state
You can check the Consul KV store by accessing the Consul UI or using the consul kv command to see the stored Terraform state:
consul kv get terraform/state