A Practical Guide to ArgoCD Security Gating
summary
Live demo shows ArgoCD + Kubescape operator running a job-based scan during an Argo Rollout that returns failure codes and blocked deployment when checks fail; the scan surfaces posture issues (privilegeEscalation true, missing resource limits) and reports two critical vulnerabilities in the image. The rollout stays on the previous version until YAML and image fixes are pushed, proving a practical pre- and post-sync security gate that stops insecure containers from reaching production.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:01Cube scape and security
- 3:12Cube scape in CI/CD
- 6:29Argo rollout for deployments
- 8:37Demo: security gating with Cube scape
- 12:15Blocking due to security failures
- 14:32Retrying secure deployment
- 18:32Final deployment after fixes
- 20:34Key takeaways
- 21:21Q&A
related talks
31mAttacking Argo CD with Argo CD (and then Defending)
34mSecure by Default with GitOps - A Guide to OPA with Argo CD
10mThe Power of OPA Gatekeeper: Enforcing Kubernetes Access Control to secure your runtime
32mIntroduction to ArgoCD
46mFrom FTP to ArgoCD & Argo Rollouts: An adoption history inside a corp
26mThreat Model Report: Security Considerations for Hardening D...
27mExploring Argo
25mArgo CD Ephemeral Access in Action: Lessons Learned While Runnin...