Flux Security Deep Dive
summary
Flux v2 defines an authorization model that maps to Kubernetes RBAC and uses the impersonation API so controllers act under tenant-scoped service accounts; controllers run non‑root with read‑only filesystems, dropped capabilities, and no shelling out. Sources include git, Helm, OCI, and S3; Git integration uses gogit and libgit2. Secrets decrypt with sops decryption (supporting KMS and age), releases are cosign-signed images with a two‑week cadence, automated CI/e2e on amd64 and arm64, and four post‑v2 high/critical CVEs motivated hardening and kubeconfig sanitization.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:54Flux - Project overview
- 4:26Flux - GitOps Continuous Delivery
- 9:07What is Flux made of?
- 17:12Flux -release pipeline
- 22:00Flux -release artifacts
- 23:38Flux vs competition?
- 26:09Who trusts in Flux?
- 27:16How secure is Flux ?
- 28:59Is Flux bulletproof?
- 30:00How to keep Flux up-to-date?
- 32:56Are my secrets safe in Git?
- 34:29Secrets operations
- 36:23Tenant isolation boundaries
related talks
09mLightning Talk: Hiding in Plain Sight - How Flux Decrypts Secrets
06mFrom Policy to Production: Flux and GitOps as Governance Control...
21mFlux at the Point of Change - Using the K8s Golang SDK and the Flux Api to Automatically Fix and Deploy CVEs in Your Base Images
39mCreating A Landlord for Multi-tenant K8s Using Flux, Gatekeeper, Helm, and Friends
20mSecure Delivery Using Flux and Open Component Model
27mHigh-Security, Zero-Connectivity & Air-Gapped Clouds: Delivering Complex Software with the Open Component Model & Flux
28mEnabling Kubeflow with Enterprise-Grade Auth for On-Prem Deployments
29mDeveloper Enablement through a GitOps Driven IaC Control Plane...