Handling secrets in kubernetes using git secrets
summary
Shows a working setup that uses git-secret + GPG to store encrypted credentials in a git repo and a set of bash helper scripts to generate and push Kubernetes secrets, mount them into pods, and trigger updates. Claims successful operation with about ~100 secrets (decrypt time scales up) and no hosted service, using the repo as the single source of truth. Limits: must re-encrypt edited files, no API for push notifications, and no hosted API.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 0:10About me
- 0:41Agenda
- 1:14Understanding the problem
- 2:15Requirements
- 3:19Solution
- 4:27Key Management
- 4:51Demo
- 6:10Adding secrets
- 7:59Interacting with kubernetes
- 14:35Pros Cons
- 16:33Outro
related talks
29mSecuring secrets in the GitOps era
43mSecuring Secrets in the GitOps Era
46mSecuring Secrets in the GitOps era
29m100,000 Different Ways to Manage Secrets in GitOps
24mUnlocking the Secrets to Effective Secrets Management in GitOps
26mSecret Management in Kubernetes: The GitOps Way - Benjamin Ritter
30mLook Ma, No secrets in my Kubernetes Cluster! - Vijay Dharap
27mGitOps, Kubernetes, and Secret Management: Don't Bake in a Tent!
