Kubernetes 1.33 introduces control-plane minor-version rollback, allowing cluster operators to safely revert upgrades if issues arise. The feature uses an "emulated version" concept that creates a two-step upgrade process: first upgrading binaries while maintaining the old API version, then finalizing the upgrade after validation. This eliminates the previous one-way upgrade path that forced rolling forward with fixes. The capability is available in open-source Kubernetes and will be generally available in GKE 1.33, alongside other upgrade improvements like skip-version upgrades, coordinated leader election, and component health indicators.

6m read timeFrom cloud.google.com
Post cover image
Table of contents
The challenge: Why were rollbacks so hard?The solution: Emulated versions

Sort: