Update CloudOps for Kubernetes from version 2.2.x

For CloudOps for Kubernetes version 2.2 and earlier, you must update to version 2.3 before you can update to version 2.4.

The update to version 2.3 must be done in three parts. You run docker-compose up three times once for each part.

For general instructions on updating the cluster with the file docker-compose.override.yml follow the steps in Upgrading CloudOps for Kubernetes.

1. Add and set a new Docker Compose parameter TF_VAR_api_gateway_update_stage in the file docker-compose.override.yml to part_1.

2. Add and set a new Docker Compose parameter TF_VAR_hubcentral_allowed_cidr in the file docker-compose.override.yml.

   note

   The parameter TF_VAR_hubcentral_allowed_cidr replaces the TF_VAR_nexus_allowed_cidr and TF_VAR_jenkins_allowed_cidr parameters as one unified value.

3. Build and run the Docker image to update the CloudOps for Kubernetes cluster.

   With part_1 of the update process, CloudOps for Kubernetes will set up an Application Load Balancer to the Ambassador service with the subdomain central<clusterName>. This step also issues TLS certificates for the DNS names used in CloudOps for Kubernetes.

4. Set the Docker Compose parameter TF_VAR_api_gateway_update_stage to part_2 and run the Docker image.

   With part_2 of the update process, CloudOps for Kubernetes switches domain names in order to use Ambassador instead of HaProxy. Cilium and Hubble are installed if the Cloud providor is AWS.

   tip

   Before continuing to part_3, we recommend that you wait a few days to ensure that the services are being routed correctly through Ambassador.

5. Set the Docker Compose parameter TF_VAR_api_gateway_update_stage to part_3 and run the Docker image.

   With part_3 of the update process, CloudOps for Kubernetes removes HaProxy from the cluster and cleans up the unused DNS entry hubgw.

Updating the Account Management Stack

To update the Account Management stack after you update the cluster:

1. Rebuild the create-or-delete-activemq-container Jenkins job that the Account Management stack was deployed with. There are not any parameter changes to make when rebuilding the job.

2. Rebuild the create-or-delete-account-management-stack Jenkins job. There are not any parameter changes to make when rebuilding the job.

Updating the Self Managed Commerce Stack

To update the Self Managed Commerce stack after you update the cluster:

1. Rebuild the info-page if the Self Managed Commerce stack was deployed with the job parameter includeDeploymentInfoPage set to true.

2. Rebuild the create-or-delete-activemq-container Jenkins job that the Self Managed Commerce stack was deployed with. There are no parameter changes to make when rebuilding the job.

3. Rebuild the deploy-or-delete-commerce-stack Jenkins job. Set the allowedCIDRs job parameter.

   note

   The new job parameter allowedCIDRs replaces the cmAllowedCIDR, integrationAllowedCIDR, cortexAllowedCIDR, studioAllowedCIDR, and infoPageAllowedCIDR parameters as one unified value.

   ---

   The new job parameters infoPageSubDomain, cortexSubDomain, cmSubDomain, and integrationSubDomain replace the dnsSubDomain parameter as separate values.

   If the Self Managed Commerce stack was originally deployed by the deploy-or-delete-ep-stack Jenkins job, it is not possible to update the stack. Instead, delete the existing stack and deploy a new one with the deploy-or-delete-commerce-stack job with the desired parameters.