I'm setting up Flux CD for business and collaborative projects, and Infisical's free plan feels restrictive. I'd prefer to keep the secrets manager outside the cluster without spending too much. What options are worth considering?
What secrets manager would you pair with Flux CD?
Answers
If keeping encrypted secrets in Git works for you, look at SOPS with age. Flux can decrypt SOPS files through its Kustomization configuration, so you don't need to run a separate secrets manager.
Keep the age private keys out of Git, use separate keys for environments, and decide how you'll recover them if the cluster is down. For a larger team, a cloud KMS may make key access easier to manage than distributing age keys, though it adds a service dependency and cost.
Reply to this answer
External Secrets Operator is worth considering if you want the secrets stored outside the cluster. Flux can manage the ExternalSecret resources, while the operator pulls values from a backend such as AWS Secrets Manager, Azure Key Vault, or OpenBao into Kubernetes Secrets.
That separation gives you some flexibility to change backends later, although authentication and backend configuration still need work. Check the provider's current pricing and collaboration limits, including request costs, before picking one. A longer refresh interval can reduce polling if your secrets don't change often.
m.827+claywicket:
Also check how your workloads pick up changes. Updating a Kubernetes Secret doesn't necessarily restart a workload, so a tool such as Reloader may help.
Reply to this answer
For a self-hosted service, OpenBao or HashiCorp Vault outside the cluster could work, with External Secrets Operator connecting to it. Both offer more of a dedicated secrets-management setup than encrypted files in Git.
The catch is that the service becomes infrastructure you have to operate and recover. Think through backups, authentication, availability, and seal and unseal procedures before relying on it for business projects. That overhead may be more than a small group wants.
Reply to this answer
For a small project, Sealed Secrets is another option if you're happy with a controller in the cluster. It lets you store encrypted secrets in Git, but it isn't the same thing as having a separate secrets manager outside the cluster. Make sure the controller's keys can be recovered.
Reply to this answer
If you mainly want to avoid running another service, compare hosted tools such as Doppler or Bitwarden Secrets Manager with the cloud provider options. Check collaborator limits and operator integration as well as the base price. A free tier that works for one project may not cover several teams.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Nerxilo-2v:
This is a good fit when the Git workflow matters more than having a separate interface for managing secrets. Key recovery still needs a plan.