1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
The case that you describe is not possible: see https://docs.aws.amazon.com/eks/latest/userguide/kubernetes-versions.html
Clusters are automatically upgraded at the end of the 26-month cycle.
What will happen at the end of 12 months of extended support?
Clusters running on a Kubernetes version that has completed its 26-month lifecycle (14 months
of standard support plus 12 months of extended support) will be auto-upgraded to the next version.
On the end of extended support date, you can no longer create new Amazon EKS clusters with
the unsupported version. Existing control planes are automatically updated by Amazon EKS
to the earliest supported version through a gradual deployment process after the end of support
date. After the automatic control plane update, make sure to manually update cluster add-ons
and Amazon EC2 nodes. For more information, see Update the Kubernetes version for your Amazon
EKS cluster.
Best,
Didier
Relevant content
- asked 7 months ago
- asked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
Hello, Thanks for your response. However, when I check my cluster whether from the aws console or with the eksctl commands, it says that the version is 1.22 (it wasn't auto-upgraded to the next version it seems). Any explanation for the reason? Thanks in advance