EKS Kubernetes Version Upgrade
EKS Kubernetes Version Upgrade
Below are steps on how to upgrade the Kubernetes version in AWS Kubernetes Service (EKS).
First, ensure that the current version is compatible with the K8S version you will upgrade to. If not, upgrade the Sisense version compatible with the K8S version first!
It is also strongly recommended to have the cloud_autoscaler feature enabled in your configuration yaml.
Upgrade the control plane of the cluster, open the EKS page, and find your cluster. You should see the 'Upgrade now' link if a newer major K8S version is available.
Click on that link and select the version (Please note, usually, only one version is available because you cannot jump over versions).
Click the Update button, and you should see a similar information bar as the one below:
The cluster is being updated:
As the control plane upgrade is being completed, the cluster version should also update as well:
If needed, the kubectl version (client binary file) should be updated manually. It should be one value more or less than the server version, e.g., for the cluster with EKS 1.23, you can use kubectl 1.22, 1.23, and 1.24.
Please notice that the nodes are still running the previous Kubernetes version.
Open the cluster page and go to the Compute tab.
You should see the upgrade options for NodeGroups.
Click on update for every node group and select "Force Update."
The new nodes should appear while the old nodes are cordoned.
Eventually, you should see only new nodes running:
If you had the cloud_autoscaled feature disabled, run the installer with the new node names.
