Drift Prevention in GitOps Workflows Using Kyverno - Omolade Akinwumi, DevOps Engineer/Founder @MAX

Don't miss out! Join us at our next KubeCon + CloudNativeCon events in Mumbai, India (18-19 June, 2026), Yokohama, Japan (29-30 July, 2026), and Shanghai, China (8-9 September, 2026). Connect with our current graduated, incubating, and sandbox projects as the community gathers to further the education and advancement of cloud native computing. Learn more at https://kubecon.io

Drift Prevention in GitOps Workflows Using Kyverno - Omolade Akinwumi, DevOps Engineer/Founder @MAX

You deployed a clean, Git-approved config and three days later, something in your cluster quietly changed and nobody knows why. That's drift. And in GitOps, it's the silent killer of everything you thought was under control. GitOps promises that your Git repo is the single source of truth. But in reality, someone makes a "temporary" fix directly on the cluster. A script runs in the wrong environment. Suddenly your cluster and your Git repo are telling two different stories, and you only find out when something breaks in production. This is where Kyverno comes in. Rather than detecting drift after it happens, Kyverno lets you write policies that prevent it entirely. Nothing gets into the cluster unless it came through the right door. This session walks through how GitOps and policy as code reinforce each other. ArgoCD keeps things in sync, Kyverno enforces what can be synced, creating a workflow where your cluster does exactly what Git says, and only what Git says. This session explores how combining GitOps with policy as code turns your delivery workflow from a promise into a guarantee.

Видео Drift Prevention in GitOps Workflows Using Kyverno - Omolade Akinwumi, DevOps Engineer/Founder @MAX канала CNCF [Cloud Native Computing Foundation]