Declarative by Default, Secure by Design: GitOps as a Control Plane for Governance
summary
GitOps becomes a universal control plane: git as single source of truth, Flux and Argo CD continuously reconcile cluster state, and a recently released MCP server for Flux exists but is attacked in the wild so run it immutable and keep a human in the loop. Policy-as-code (linked to NIST/PCI/DORA) enforces and upgrades across hundreds or thousands of clusters, enables continuous compliance, and reduces audit pain; expect 70–90% LLM suggestions to be useful but risky for automated writes. Terraform/OpenTofu state and Common Cloud Controls matter for non‑Kubernetes drift.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 2:28GitOps as governance control plane
- 8:11Governance fails without GitOps
- 11:20GitOps as universal control plane
- 13:47Policy as code for compliance
- 16:16Key takeaways and future
- 18:06Q&A
related talks
06mFrom Policy to Production: Flux and GitOps as Governance Control...
48mThe State of GitOps in 2021
07mIntroduction to GitOps
09mOpening and Welcome
33mThe Role of GitOps in IT Strategy
05mAgentic GitOps: Evolving Enterprise Delivery
26mKeynote Session: GitOps as an Evolution of Kubernetes
34mGitOps Is Likely More Than You Think It Is