Amazon Elastic Kubernetes Service (Amazon EKS) is a managed service that you can use to run Kubernetes on AWS without needing to install, operate, and maintain your own Kubernetes control plane or nodes. EKS runs upstream Kubernetes and is certified Kubernetes conformant for a predictable experience.
| Release | Released | End of Support | Latest |
|---|---|---|---|
| 1.24 |
1 month and 5 days ago (15 Nov 2022)
|
Ends
in 1 year (01 Jan 2024)
|
1.24-eks-3
(05 Dec 2022)
|
| 1.23 |
4 months ago (11 Aug 2022)
|
Ends
in 9 months (01 Oct 2023)
|
1.23-eks-5
(05 Dec 2022)
|
| 1.22 |
8 months ago (04 Apr 2022)
|
Ends
in 4 months (01 May 2023)
|
1.22-eks-9
(05 Dec 2022)
|
| 1.21 |
1 year and 5 months ago (19 Jul 2021)
|
Ends
in 1 month and 3 weeks (15 Feb 2023)
|
1.21-eks-14
(05 Dec 2022)
|
| 1.20 |
1 year and 7 months ago (18 May 2021)
|
Ended
1 month and 2 weeks ago (01 Nov 2022)
|
1.20-eks-12 |
| 1.19 |
1 year and 10 months ago (16 Feb 2021)
|
Ended
4 months and 3 weeks ago (01 Aug 2022)
|
1.19-eks-11 |
| 1.18 |
2 years ago (13 Oct 2020)
|
Ended
8 months ago (31 Mar 2022)
|
1.18-eks-13 |
Amazon EKS guarantees support for at least four production-ready versions of Kubernetes at any given time. A Kubernetes version is fully supported on EKS for 14 months after first being available on Amazon EKS. This is true even if upstream Kubernetes is no longer supporting a version available on Amazon EKS.
You can subscribe to upgrade notices (sent approximately 12 months after the Kubernetes version was released on Amazon EKS) on your Personal Health Dashboard. The notice includes the end of support date, which is at least 60 days from the date of the notice.
Upgrading
Amazon EKS will automatically upgrade existing control planes (not nodes) to the oldest supported version through a gradual deployment process after the end of support date. After the automatic control plane update, you must manually update cluster add-ons and Amazon EC2 nodes. Amazon EKS does not allow control planes to stay on a version that has reached end of support.
Because Amazon EKS runs a highly available control plane, you can update only one minor version at a time. Therefore, if your current version is 1.19, and you want to update to 1.21, then you must first update your cluster to 1.20 and then update it from 1.20 to 1.21. Similarly, your node version can be at most 2 minor version behind the control plane version.
Clusters are always created with the latest available Amazon EKS platform version (eks.n) for the specified Kubernetes version. If you update your cluster to a new Kubernetes minor version, your cluster receives the current Amazon EKS platform version for the Kubernetes minor version that you updated to.
New Amazon EKS platform versions don’t introduce breaking changes or cause service interruptions.
Platform Versions
Not every Kubernetes patch release is published on EKS. EKS releases follow a “platform versioning”, which starts at eks.1 for each Kubernetes minor version. The Platform Versions lists the underlying Kubernetes version used in each EKS platform version.
More information is available on the Amazon EKS website.
You should be running one of the supported release numbers listed above in the rightmost column.
eksctl get cluster --name=cluster-name
You can submit an improvement to this page
on GitHub
. This page has a corresponding Talk Page.
A JSON version of this page is available at /api/amazon-eks.json. See the API Documentation for more.
This page was last updated on 14 December 2022. Latest releases are automatically updated.