Update from version 2.5.0

important

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 CloudOps for Kubernetes cluster on AWS

To update the CloudOps for Kubernetes cluster from release 2.5.x on AWS, use the following steps. The update to version 2.6.x must be done by modifying the docker-compose.override.yml file.

1. In the docker-compose.override.yml file, add a new Docker Compose parameter called TF_VAR_updating_from_pre26.

2. Set the parameter to true.

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

   During the process of updating the cluster from release 2.5.x, CloudOps for Kubernetes removes the previous Container Network Interface (CNI) chaining configuration of Cilium. It installs Cilium with Elastic Network Interfaces (ENI) allocation configuration enabled on AWS. After the update of the Cilium deployment is complete, the AWS node groups rebuild. The AWS node DaemonSet is marked to be permanently unavailable to force the pods to use Cilium after the rebuild. After the node groups rebuild, the rest of the cluster updates.

   tip

   To create a brand new cluster, open the docker-compose.override.yml file and set the TF_VAR_updating_from_pre26 parameter to false. The setting ignores the unique update process and installs Cilium with Elastic Network Interfaces (ENI) allocation enabled on AWS. After the creation of the cluster is complete, the AWS node groups rebuild. The AWS node DaemonSet is unavailable.

Updating the Account Management Stack

After you update the cluster, 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

Use the following steps to update the Self Managed Commerce stack after you add the Ambassador ingress controller to your cluster.

• 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.