Prerequisites
To upgrade your CloudBlue Commerce installation to version 20.5, ensure that the following requirements are met:
- The Kubernetes version on your source installation before CloudBlue Commerce upgrade must be below 1.16.
- CloudBlue Commerce upgrades to 20.5 can be performed on installations with:
- Operations of version 20.4
- Billing of version 20.4
- CloudBlue Commerce upgrades to version 20.5 using the cumulative upgrade scenario can be performed on installations with:
- Operations of version 7.1
- Billing of version 7.1
Important:
1. If you have the WebHosting Plesk module installed, you cannot use the cumulative upgrade scenario to upgrade CloudBlue Commerce to 20.5. Use the regular upgrade scenario.
2. If you have the Cloud Infrastructure Automation module installed, you can use the cumulative upgrade scenario to upgrade CloudBlue Commerce on installations with Odin Automation version 7.4 and later, with Cloud Infrastructure Automation version 18.0.16, to 20.5.
3. If you upgrade from an Odin Automation version earlier than 8.0 and the upgrade to 8.0 requires EOL-related actions, you must perform these actions before the upgrade. - (Optional) Remove the Windows Shared Hosting and Linux Shared Hosting modules from your CloudBlue Commerce installation before upgrade to version 8.0 when using the cumulative upgrade. For details, refer to these articles: https://kb.cloudblue.com/en/132851 and https://kb.cloudblue.com/en/132897.
- (Optional) If you have the Cloud Infrastructure Automation module installed, upgrade it to version 18.0.16 prior to the platform upgrade.
- Service nodes must run version 6.x. or higher of RHEL or CentOS.
-
For the SELinux policies to be correctly installed during the upgrade, update the selinux-policy-targeted package to version 3.13.1-229 or higher on the following nodes registered in CloudBlue Commerce:
- CloudBlue Commerce MN
- Operations DB
- Billing application
- Billing database
- Billing online store
- CloudBlue Commerce UI
- CloudBlue Commerce branding
- Privacy Proxy
- DNS
- Domain Registrar Plug-ins
- APS Endpoint nodes
- APS proxy node
- Components cluster nodes
Note: On nodes, where the selinux-policy-targeted package was not updated, SELinux policies can be deployed manually after upgrade to 20.5.