Update from version 2.9.0

Perform the Update

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

Additional Steps

The following additional steps are required when you update from CloudOps for Kubernetes release 2.9.x.

Updating the Self Managed Commerce Stack

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 begin using the new Tomcat and Java versions in the Self Managed Commerce Stacks.

note

Ensure that you are using the latest version of Elastic Path Docker repository compatible with CloudOps for Kubernetes v2.10.x.

1. Rebuild the Tomcat base image and any Commerce Docker images based on this base image with the build-selected-docker-images Jenkins job.

   note

   Make sure to use a unique and relevant value in the imageTag parameter.

   The following parameters must be set to true to rebuild all the images that use Tomcat and Java:

   • buildBase
   • buildCortex
   • buildSearch
   • buildBatch
   • buildIntegration
   • buildCm
   • buildDatasync
   • buildDatapop
   • buildMock

2. Build 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.
   • The restartApps parameter is selected.