I want to keep secret values out of a public Git repository while making a Kubernetes cluster rebuild straightforward. How well do Bitwarden Secrets Manager and External Secrets Operator fit that setup, and what still needs bootstrapping?
Is Bitwarden with External Secrets Operator a reasonable way to rebuild a homelab cluster?
Answers
That setup can work well. Store the values in Bitwarden Secrets Manager, keep references in Git, and have External Secrets Operator sync them into ordinary Kubernetes Secrets for workloads to use.
The bootstrap credential still has to come from somewhere outside Git. Scope the cluster's access to read only, protect that credential, and make sure the rebuild procedure covers getting it into the new cluster. The synced values also live in Kubernetes Secrets, so access to those needs to be controlled too.
Reply to this answer
Check the Bitwarden integration's deployment details before settling on it. The External Secrets Operator integration uses a sidecar and requires a TLS certificate, which can make the initial setup more awkward than just providing a token.
I'd test the full bootstrap on a fresh cluster, including how the certificate and token get provisioned, rather than assuming the Git definitions alone will bring everything back.
Reply to this answer
If you already run Vault or OpenBao, Kubernetes authentication is another option. Workloads can authenticate using their Kubernetes identities, and policies can restrict access to the secrets they need. External Secrets Operator supports Vault's Kubernetes auth too.
That avoids placing a separate provider token in the cluster for that authentication flow, but it doesn't erase the backend's own bootstrap and operational needs. Vault needs an unseal process after a restart, either with unseal keys or auto-unseal. Running the backend yourself also means looking after its state, backups, and upgrades.
Reply to this answer
Bitwarden isn't the only route here. A cloud secrets manager or another supported provider might be simpler if it fits the infrastructure you already have. Compare how each one authenticates the cluster and what you have to restore or provision during a rebuild.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Sunny:
Good point. The certificate setup belongs in the rebuild plan too, not just the access token.