Amazon EKS adds Kubernetes version rollback feature

Amazon EKS now offers a Kubernetes version rollback feature, enabling cluster administrators to revert to a previous minor version within seven days of an upgrade. This addresses the lack of native control plane rollback in open-source Kubernetes, providing a safety net for upgrades. The feature aims to reduce the complexity and risk associated with cluster upgrades, allowing teams to avoid extended upgrade cycles and clusters stuck on older versions.

For EKS Auto Mode clusters, version rollbacks now include managed nodes and offer a cancel API. This allows users to stop a node rollback process if it takes too long or if they wish to change their approach, providing more control over the rollback duration and sequence, respecting pod disruption budgets by default.

EKS automatically evaluates rollback readiness before a version rollback is initiated. It flags potential issues such as node version compatibility or add-on dependencies, helping to ensure a smoother rollback process. An optional --force flag is available to bypass these checks if immediate action is required.

Control plane rollbacks are supported for all EKS clusters, while node rollbacks are available for clusters using EKS Auto Mode. Version rollbacks support clusters running Kubernetes versions within EKS standard and extended support timelines. The feature is available at no additional cost in all commercial AWS Regions.