Kubernetes 1.32 End of Life: Migration Playbook for February 28, 2026

12 days. That's how long Kubernetes 1.32 has left before the upstream project stops issuing patches. After February 28, 2026, there are no more security fixes, no more bug patches, no more backports. Version 1.32.12 - released on February 10 - is the last update you will ever get. If you're still running 1.32 in production, this is your migration playbook. Not a gentle nudge. A concrete, step-by-step plan to get off a version that's about to become a liability. What "End of Life" Actually Means (It's Worse Than You Think) Let's be precise about what happens on March 1st if you're still on 1.32. No more CVE patches. When the next Kubernetes vulnerability drops - and it will - the fix will ship for 1.33, 1.34, and 1.35. Not 1.32. You'll read the advisory, understand exactly how your clusters are exposed, and have no upstream fix to apply. This isn't theoretical. Look at what's already been patched in 1.33.x that 1.32 users are exposed to right now : CVE-2025-5187 (fixed in 1.33.4): Nodes