Update from version 2.10.0
Perform the Update
Follow the general instructions on updating the cluster in the Upgrading CloudOps for Kubernetes documentation.
Additional Steps
Two changes introduced in CloudOps for Kubernetes release 2.11.x require additional steps to fully apply:
The ActiveMQ architecture is updated to always use a single ActiveMQ instance for improved data reliability.
The MySQL, ActiveMQ, and Self Managed Commerce Deployments can now run with non-root containers for improved security.
warning
You must update the ActiveMQ deployment architecture before updating the ActiveMQ deployment to run as non-root.
These steps must be done in the above order. Existing ActiveMQ deployments from CloudOps for Kubernetes release 2.10 are run using the root user. If you attempt to update the ActiveMQ architecture after updating the ActiveMQ deployment to run as non-root, the non-root user is unable to remove the lock on the kahaDB file and the migration fails.
We recommend you apply these architectural changes shortly after upgrading to CloudOps for Kubernetes release 2.11.x for the following reasons:
- You are not able to use the
create-or-delete-activemq-containerjob to manage on update your ActiveMQ deployment until you complete the steps to switch to the new ActiveMQ architecture. - You are not able to use Elastic Path Docker release
4.2or higher unless until you complete the steps to run containers as the non-root user.
These updates do not need to be completed immediately and can be done at some point after completing the general steps to update to release 2.11.x.
Instructions on applying these additional changes are given individually. Elastic Path recommends applying the changes separately: complete and validate one change before proceeding to perform the other.
Updating the ActiveMQ Deployment Architecture
Due to an issue with highly-available (HA) architecture, as of CloudOps for Kubernetes release 2.11, the ActiveMQ architecture now only uses a single ActiveMQ instance.
For more information about this change and how to update to the single ActiveMQ instance architecture see the Updating the ActiveMQ Deployments documentation.
Updating the MySQL, ActiveMQ, and Self Managed Commerce Stack Deployments to Run as Non-Root
CloudOps for Kubernetes release 2.11.x introduces the ability to run the MySQL, ActiveMQ, and Self Managed Commerce Stack containers with a non-root user app_runner with user ID 10001.
For more information about this change, how to update existing deployments to run as non-root, and how to continue deploying new deployments as root see the Update Containers to Run as Non-root documentation.