The purpose of this document is to provide an overview of the steps for upgrading the EKS Cluster from one version to another. Please note that EKS upgrade documentation gets published by AWS every year.
The current version of the upgrade documentation while writing this README
1. Download the latest upgrade docs from AWS sites (https://docs.aws.amazon.com/eks/latest/userguide/update-cluster.html)
2. Always upgrade one increment at a time (E.g., 1.17 to 1.18). AWS doesn't support upgrades from 1.16 to 1.18 directly
This table shows the supported plugin versions for each EKS Kubernetes version
| Kubernetes version | 1.19 | 1.18 | 1.17 | 1.16 | 1.15 | 1.14 |
|---|---|---|---|---|---|---|
| Amazon VPC CNI plugin | 1.7.5 | 1.7.5 | 1.7.5 | 1.7.5 | 1.7.5 | 1.7.5 |
| DNS (CoreDNS) | 1.8.0 | 1.7.0 | 1.6.6 | 1.6.6 | 1.6.6 | 1.6.6 |
| KubeProxy | 1.19.6 | 1.18.9 | 1.17.12 | 1.16.15 | 1.15.12 | 1.14.9 |
-
Change the version in Terraform to desired version under
base.tfvars. See the example belowkubernetes_version = "1.20" -
Apply the changes to the cluster with Terraform. This step will upgrade the Control Plane and Data Plane to the newer version, and it will roughly take 35 mins to 1 hour
-
Once the Cluster is upgraded to desired version then please updated the following plugins as per the instructions
Just update the latest versions in base.tfvars file as shown below. EKS Addon latest versions can be found in AWS EKS Console under Addon section or from AWS documentation.
enable_kube_proxy_addon = true
kube_proxy_addon_version = "v1.20.4-eksbuild.2"
enable_coredns_addon = true
coredns_addon_version = "v1.8.3-eksbuild.1"
enable_vpc_cni_addon = true
vpc_cni_addon_version = "v1.8.0-eksbuild.1"
Apply the changes to the cluster with Terraform.
Please note that you may need to update other Kubernetes Addons deployed through Helm Charts to match with new Kubernetes upgrade version