Amazon EKS Introduces Kubernetes Version Rollback and Extended Support

Kubernetes Version Rollback Capability

Amazon EKS has introduced support for Kubernetes version rollbacks. This feature allows users to revert a cluster's control plane to its previous Kubernetes version within seven days of an upgrade. The rollback mechanism is designed to reduce the risk associated with in-place cluster upgrades by providing a recovery option for problematic updates.

Technical Details of Rollback

When a rollback is performed, EKS reverts the Kubernetes API server and other control plane components. Importantly, all etcd data, workloads, and persistent volumes are preserved during this process. For clusters operating in EKS Auto Mode, worker nodes are automatically rolled back before the control plane, with options available to accelerate or cancel this process.

Extended Support for Kubernetes Versions

In addition to rollbacks, Amazon EKS has introduced Extended Support for Kubernetes versions. This change extends the availability of each Kubernetes version to 26 months. This aims to address operational challenges faced by organizations due to the frequent release schedule of Kubernetes, which typically sees three minor versions per year.

Addressing Upgrade Challenges

Historically, upgrading a Kubernetes control plane has been a one-way operation, meaning changes could not be reversed. This constraint often led organizations to delay upgrades, resulting in clusters running older versions, missing security patches, and eventually reaching extended support timelines. The new rollback feature and extended support period are intended to mitigate these issues, making cluster lifecycle management simpler and safer.

Impact on Cluster Management

Platform teams managing large fleets of clusters often spend weeks preparing for each in-place upgrade cycle, involving parallel infrastructure for validation and extensive pre-flight verification. Some organizations adopted blue-green deployment strategies as an insurance policy against upgrade failures. The new EKS features aim to reduce the operational cost and complexity associated with Kubernetes upgrades, providing more time for validation and coordination.