Skip to main content

Upgrade Kubernetes Version in an Ocean EKS Cluster

This page describes the procedures for upgrading the Kubernetes version in an Ocean cluster.

After you have completed all the steps described, all new nodes launched by Ocean will be launched with the new Kubernetes version.

Step 1: Upgrade your EKS Control Plane Version​

Update your EKS cluster in AWS by using the EKS guide. When the upgrade is completed, follow the next steps.

Step 2: Update Nodes to the Same Kubernetes Version as your Control Plane​

After the EKS control plane is upgraded, you need to change the AMI in Ocean, based on the Kubernetes version you upgraded. In the AWS documentation, you can view the list of EKS Optimized AMIs.

You can change the AMI in one of the following ways:

  • If you use the same AMI for all of your workloads, you should change the AMI on the Ocean cluster level by editing the Default VNG/ Template VNG. This can be done using the Spot console or the Spot API.

Ensure that the AMI value in the custom VNG is null if you are using this method.

OR

  • If you want to use a different AMI for your custom VNGs, change the value of each VNG using the Spot Console or the Spot API.

Tip: You should change the AMI of custom VNGs if they use different AMIs than the default VNG.

Step 3: Roll the Cluster​

The cluster roll process enables you to make changes in order to align cluster infrastructure with a new image, user data, or security groups, without having to disable the Ocean Autoscaler or manually detach nodes in the cluster.

Rolls can be triggered for the whole Ocean cluster, per VNG, or per instance. You may trigger the process using the Spot console or the Spot API.

Once the roll is complete, all of the nodes in the cluster will have the new Kubernetes version.

Tip: New Kubernetes versions sometimes introduce significant changes. Spot recommends testing the behavior of your applications in a Dev cluster against a new Kubernetes version before updating your production clusters.