Update from version 2.7.0

important

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

note

During the process of updating the cluster from release 2.7.x, CloudOps for Kubernetes removes the previous AWS Web Application Firewall (WAF) configuration and the Ambassador load balancing configuration. After the previous WAF and load balancing configurations are removed, the rest of the cluster updates. As the cluster updates, a new load balancing solution is created using HAProxy and a new WAF configuration using ModSecurity. During this update, your Nexus and Jenkins instances will experience some down time. Your Elastic Path Account Management and Self Managed Commerce stacks will remain inaccessible until you complete the following update steps below.

Performing the Update

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

warning

There will be a Self Managed Commerce outage once you begin running the docker-compose up step. Your Self Managed Commerce services will be offline and unavailable for the duration of the upgrade starting at that step, when upgrading from CloudOps for Kubernetes release 2.7.x. The outage will be resolved at the end of the upgrade process.

Additional Steps

The following are additional steps required when updating from CloudOps for Kubernetes release 2.7.x.

Updating the Self Managed Commerce Stack

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. This is required to add the ingress configuration to the new HAProxy ingress controller.

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

2. Build the create-or-delete-activemq-container Jenkins job with the kubernetesNickname parameter set to the namespace of the previously deployed Self Managed Commerce stack and the cloudOpsForKubernetesBranch parameter set to the new release branch.

note

The outage of the Self Managed Commerce environment will be resolved when the above steps are completed.

Updating the Account Management Stack

note

This step applies only to customers who previously deployed the now-deprecated Elastic Path Account Management feature.

Use the following steps to update the the Account Management stack after you complete the general upgrade steps to update the cluster, including any required manual steps such as addressing Jenkins plugin issues.

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 and the cloudOpsForKubernetesBranch parameter set to the new release branch.

2. 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 and the cloudops_for_kubernetes_branch parameter set to the new release branch.