Update to version 2.12

Prerequisites

Complete the upgrade to CloudOps for Kubernetes release 2.11.x before upgrading to release 2.12.x.

Perform the Update

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

Additional Steps

CloudOps for Kubernetes release 2.12.x updated the Kubernetes version to 1.22 and requires additional steps to be fully applied:

• Update existing services to use the new ingress API version. To do this, complete the rest of the steps on this page.

We recommend you apply these changes shortly after upgrading to CloudOps for Kubernetes release 2.12.x for the following reason:

• You will not be able to manage the deployments through Terraform if they were deployed before upgrading to CloudOps for Kubernetes release 2.12.x until you complete the steps to switch to the new ingress API resource.

Elastic Path recommends applying the changes separately: complete and validate one change before proceeding to perform the other.

Updating the ingresses on ActiveMQ, and Self Managed Commerce stack deployments

Ensure that you first complete the general upgrade steps to update the cluster, including any required manual steps, such as addressing Jenkins plugin issues. Then, repeat the following steps for each of your Self Managed Commerce stacks. These steps are required to migrate to the new ingress API resource.

1. Run the create-or-delete-activemq-container Jenkins job.

   Use the kubernetesNickname parameter set to the namespace of the previously deployed ActiveMQ container and the parameters you used when you previously ran the create-or-delete-activemq-container Jenkins job. Ensure that:

   • The cloudOpsForKubernetesBranch parameter is set to the new release branch.
   • The dockerImageTag is set to the same value as the imageTag parameter from the Jenkins job build-selected-docker-images.

2. Run the deploy-or-delete-commerce-stack Jenkins job.

   Use the kubernetesNickname parameter set to the namespace of the previously deployed Self Managed Commerce stack and the parameters you used when you previously ran the deploy-or-delete-commerce-stack Jenkins job. Ensure that:

   • The cloudOpsForKubernetesBranch parameter is set to the new release branch.
   • The dockerImageTag is set to the same value as the imageTag parameter from the Jenkins job build-selected-docker-images.