Scaling Developer Self-Service: Kyverno Policies for Inclusive Platform Engineering
summary
Kyverno policy automation enforces, mutates, and generates resources so developers deploy safely without blockers: policies inject resource limits and add network policies or sidecars, validate manifests, and emit reports. Real results: 78% reduction in failed deployments and 65% higher junior-developer confidence after mutation-driven defaults. Platform pattern: start with mutation policies, use generate for missing infrastructure, and iterate on policy reports and adoption metrics (failed deployments, self-service adoption, time-to-production) to shift shadow IT into governed self-service.
AI-written summary · about
chapters (11)
- 0:00Inclusive platform engineering
- 2:28Kubernetes adoption problems
- 4:14Kyverno for developer autonomy
- 7:26Guardrails vs gatekeeping
- 9:54Shadow IT with Kyverno
- 12:03Measuring platform inclusivity
- 13:50Key lessons for engineering
- 14:55Call to action for Kyverno
- 15:15Demo: resource limits in Kubernetes
- 17:25Compliance in payment systems
- 18:33Q&A
related talks
39mKyverno Playground: Make Policy Testing a Breeze and Enjoy the Process!
11mBuilding Scalable Developer Platforms
10mCompliance as Code Meets Developer Portals: Kyverno + Backstage in...
54mDeveloper experience platforms
26mBuilding Internal Platforms to Enhance Developer Experience
34mChoose Your Own Adventure: The Dignified Pursuit of a Developer Platf...
38mShift Down Security! How Platform Teams Can Help Break the Logjam
27mWhy Developer Platforms and a curated Dev Experience are a must have when scaling