unkinben
680a0455e5
Instead of generating cluster-wide RBAC, the agent-dns role now mints tokens for a static GitOps-managed service account (argocd-apps#332) whose per-namespace RoleBindings confine access to exactly the four bind namespaces. Ordering: the argocd-apps RBAC must sync before these creds are usable, since Vault mints tokens for an SA that must already exist. - extend the kubernetes_secret_backend_role module with an optional service_account_name; when set, generated_role_rules and kubernetes_role_type are omitted (the SA's own bindings supply RBAC). - switch the agent-dns role to service_account_name agent-dns with allowed_kubernetes_namespaces bind-system; drop its generated rules. Claude-Session: https://claude.ai/code/session_01JUoARVdmhxKQHyyyp1pxeT
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