Policy-Based GitOps: How Policies Can Help Secure and Automate GitOps...
summary
Demonstrates that combining Argo CD, Kyverno and Cluster API automates secure self‑service cluster provisioning: creating a namespaced resource triggers Cluster API to provision a tenant cluster, ArgoCD ApplicationSets install Calico and the Kyverno controller, and Kyverno validates image signatures, blocks :latest tags, enforces probes/requests and generation of namespace RBAC. Cites an Argo user study (>80% run ArgoCD in production, >66% >6 months). The demo provisions clusters and enforces guardrails end‑to‑end successfully.
AI-written summary · about
chapters (8)
- 0:00Start
- 2:06What doesn't work well
- 5:49Kyverno policies
- 9:02Challenges and solutions
- 11:33Management Cluster Setup
- 22:16Demo
- 22:45Enhancements
- 23:40Key takeaways
related talks
27mSecure by Design: Embedding DevSecOps into Your GitOps Workflows
23mEmpower Developers with GitOps-Driven Kubernetes Cluster Provisioning
27mImplementing GitOps with ArgoCD: A Practical Guide
34mSecure by Default with GitOps - A Guide to OPA with Argo CD
28mHow To Automate Your Governance Strategy for Hundreds of Kubernetes Clusters
05mLessons from a Large-Scale GitOps Implementation
30mManage your kubernetes cluster in the GITOPS way !!
36mKEYNOTE: Taking a step back and leveraging GitOps to wrangle your clusters and projects