Update to Version 3.4 · CloudOps for Kubernetes

Prerequisites

CloudOps for Kubernetes 3.4.x has the following pre-requisites.

CloudOps for Kubernetes `3.3.x`

Complete the upgrade to CloudOps for Kubernetes release 3.3.x before upgrading to release 3.4.x. For instructions on upgrading to release 3.3.x, see Update to Version 3.3.

What Has Changed

For a list of the changes in the release, see Release Notes.

Changes that impact the upgrade process

CloudOps for Kubernetes release 3.4.x contains the following changes that impact the upgrade process.

The Kubernetes version is updated from 1.29 to 1.31, and various tools that are dependent on the Kubernetes version have also been updated. For more information on the changes, see End of Support for EKS 1.29.
The supported Linux operating system version for the EKS cluster nodes has changed from Amazon Linux 2 to Amazon Linux 2023. If you have been using a custom Amazon Machine Image (AMI) based on Amazon Linux 2 update it to Amazon Linux 2023. One way to determine if you have been using a custom AMI is to view your docker-compose.override.yml file and see if a value was specified for parameter aws_eks_ami.

Preparation

Review all upgrade steps and requirements described in this document.
Review all upgrade steps and requirements described in Upgrading CloudOps for Kubernetes.
Document an upgrade plan with all steps that you will need to perform to complete the upgrade. Include validation steps in the upgrade plan. Validation should include the functionality of Jenkins jobs, Commerce services, and any custom tools.
Suggested: practice and refine the upgrade plan in an AWS account that is not used by other members of your team or by the business. For example, obtain an empty AWS account, setup CloudOps for Kubernetes release 3.3.x and Commerce services in that account, then follow your upgrade plan to apply the CloudOps for Kubernetes update.
Identify a time to apply the CloudOps for Kubernetes update to your production cluster. As part of the upgrade process you will need to rebuild the nodegroups because of the Kubernetes version change. There will likely be a Self Managed Commerce service outage while the EKS node groups are rebuilt. A Self Managed Commerce service outage duration of up to 15 minutes has been observed in our testing.

Perform the Update

Follow the general instructions on updating the cluster in the Upgrading CloudOps for Kubernetes documentation.