Update from version 2.3.0

To update the CloudOps for Kubernetes cluster from release 2.3.x, use the following instructions.

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

Updating the Account Management Stack

Update the cluster and then use the following steps to update the Account Management stack:

1. Build the create-or-delete-account-management-activemq-container Jenkins job with the TF_VAR_kubernetes_nickname parameter set to the namespace of the previously-deployed Account Management stack.

2. Build the create-or-delete-account-management-mysql-container Jenkins job with the TF_VAR_kubernetes_nickname parameter set to the namespace of the previously-deployed Account Management stack.

3. Rebuild the create-or-delete-account-management-stack Jenkins job with the TF_VAR_kubernetes_nickname parameter set to the namespace of the previously-deployed Account Management stack.

Updating the Self Managed Commerce Stack

To update the Self Managed Commerce stack after you have added the Ambassador ingress controller to your cluster, use the following steps:

1. Build the deploy-or-delete-commerce-stack Jenkins job with the same parameters that you used when you previously ran the deploy-or-delete-commerce-stack Jenkins job. Optionally, set the following parameters:

   • restartApps- If you want to force a restart of the Commerce deployments during the update, set restartApps to true.
   • TF_VAR_enable_firewall_rules- If you previously ran the deploy-or-delete-commerce-stack Jenkins job with the enable_firewall_rules parameter set to true, set TF_VAR_enable_firewall_rules to true.