Mount the rancher secrets engine + seed a service account + roles #93
Reference in New Issue
Block a user
Delete Branch "benvin/rancher-secrets-engine"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
Deploy the new Rancher token secrets engine into the cluster (the last of the 4 wiring PRs), mirroring the litellm/gpg pattern. Users can then
vault read rancher/creds/<role>for short-lived, cluster-scoped Rancher tokens, backed by a seeded admin token the engine auto-rotates before Rancher's 90-day cap.Changes
rancher_secret_backendmodule — mount + config via the ranchervaultsecret provider (rancher_urlhttps://rancher.k8s.syd1.au.unkin.net).rancher_secret_backend_service_accountmodule — seeds an auto-rotated token (90d TTL / 45d rotation); the seed token is read from KV, not git.rancher_secret_backend_rolemodule + acirole (1h/8h, cluster+TTL scoped).config.hcldiscovery, module variables,main.tfblocks, terragrunt inputs, and therancherprovider inroot.hcl.config/rancher_secret_backend/rancher.yaml,.../service_account/rancher/admin.yaml,.../role/rancher/ci.yaml.Prerequisite
Populate
kv/service/vault/au/syd1/secret_backend/rancher/service_account/adminwith a live Rancher admin token (keys:token, optionaltoken_name) before apply, exactly as litellm'smaster_keyis seeded in KV.Merge order
Part 4 of 4 (last). Requires: puppet install (#483) → deployer policy (#91) → plugin import (#92) → this. The
planneeds the KV seed present, so seed KV first.View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.