Upgrade EKS to 1.31

a)     This will only present one. In this case it will be 1.30 (the next minor version)

3) After the eks version upgrade complete, you could click upgrade now again to upgrade eks to 1.31

4)     Update the nodegroups by going to EKS > Clusters > cluster-name and select the Compute tab.

a)     You will see a similar list to the ones below (with system nodegroup, presto nodegroup, etc.)

b)     You can update all presto clusters. All nodegroups (worker and coordinator) related to the cluster must also be updated. (Upgrade presto nodegroup will have downtime)

c)     Also update system nodegroup.

d)     If standalone prometheus is enabled, there will be a system-prometheus nodegroup, update that as well.

Important!!! If you have multiple launch template, when updating nodegroups, check Change launch template version and choose the latest template version.

5) 

1)     In the same page EKS > Clusters > cluster-name, select the Add-ons tab.

a)     Update the addons to the Default version set by AWS

b)     If Add-on access needs to be selected, choose IAM roles for service accounts (IRSA)

6)     Once all the updates have finished you can proceed with testing your compute plane for continuity of operation by doing the following methods: a) Verify cluster and node versions match

i)      Navigate to the AWS Management Console > EKS > Clusters, Kubernetes version should be 1.31

ii)    Navigate to the EKS > Clusters > cluster-name and select the Compute tab. In the

Node groups section, all node group should also have Kubernetes version 1.31