Exploring HashiCorp Vault and ArgoCD the GitOps Way
summary
Compares HashiCorp Vault vs file-based GitOps secrets (Bitnami Sealed Secrets, sops, Kubernetes Secrets) and demonstrates a working ArgoCD pipeline that deploys without committing secrets by using Vault kv v2 and the Vault Agent Injector to auto‑mount and rotate credentials; notes alternatives like the argo‑vault‑plugin and the CSI driver with Vault provider, discusses reconciliation gaps, inability to declare Vault easily in Git, and shows the setup actually running with no secret blobs in Git.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:47What is GitOps
- 2:35Argo CD explained
- 4:01Managing secrets in GitOps
- 8:54HashiCorp Vault overview
- 11:03Vault and Argo CD integration
- 13:51Conclusion and Q&A
related talks
10mLightning Talk: Exploring HashiCorp Vault and ArgoCD - the GitOps Way
35mShh, It’s a Secret: Managing Your Secrets in a GitOps Way
25mGitOps and Secrets: State of the Union
48mEffortless Secrets Management in Kubernetes
23mUsing Hashicorp Vault in Kubernetes Clusters
29m100,000 Different Ways to Manage Secrets in GitOps
10mLightning Talk: How to Keep a Secret in GitOps, Without Keeping...
27mImplementing GitOps with ArgoCD: A Practical Guide