When upgrading from an HCL™ Accelerate version prior to 2.4.0 for Kubernetes and OpenShift upgrades, you are required to perform a Helm uninstall and install prior to performing a full installation of version 2.4.x.
For Docker Compose upgrades of HCL Accelerate with a default certificate replaced with a custom certificate, the installer tracks the latter certificate and reads the associated files from the directory location.
When upgrading from an HCL Accelerate version prior to 2.4.0 for Kubernetes and OpenShift upgrades, you are required to perform a Helm uninstall and install prior to performing a full installation of version 2.4.x.
The Jenkins UrbanCode Velocity plug-in is now prerequisite and must be installed. The allows for running Jenkins jobs as a part of a deployment plan inHCL Accelerate. Version 2.1.0 of the plug-in is required. For more information about the plugin, see the Jenkins website.
Drops Support for MongoDB 3.4
Starting in HCL™ Accelerate v2.0.0, the MongoDB server 3.4 is no longer supported. HCL™ Accelerate v2.0.0 supports MongoDB server versions: 3.6, 4.0, and 4.2. For more information about out of service MongoDB server versions, see Mongo website. Docker Compose installations automatically upgrade to 3.6. Helm installations require manual upgrade or installation of the MongoDB server to 3.6 or later. New Helm installations use MongoDB 4.2 according to the Helm chart.
Improves Upgrade Support for all Prior Versions
All versions can be directly upgraded to 1.5.1 or later. Helm upgrades from 1.4.5 and 1.5.0 avoid previous complications. HCL™ Accelerate 1.5.1 also fixes an old issue that required versions older than 1.2.6 to upgrade to 1.2.6 before upgrading further.
Note: Helm upgrades from versions prior to 1.5.0 still require helm delete --purge <release_name>
Introduces Purge Requirement for Upgrade of Older Helm Installations
Starting with v1.5.0, we have added and modified some Helm Selectors to adhere with best practices. Therefore, running the helm upgrade command from a previous version of HCL™ Accelerate fails. All upgrades from a version prior to v.1.5.0 to v1.5.0 or later will require a Helm purge as described below. Delete your currently installed release with helm delete --purge <release_name>, where <release_name> is the name of your current UrbanCode velocity release. Follow the normal install directions with all previous name and values from your previous release.
Note: Your Mongo database will be not be modified as it is maintained outside of the installation.
Introduces MongoDB Support and Upgrade Cadence
In v1.4.5, the distributed version of MongoDB was upgraded from v3.4 to v3.6. Docker Compose installs will see the upgrade happen automatically. Other Docker platforms (OpenShift, Kubernetes, etc), will need to manually upgrade their MongoDB instance. MongoDB v3.4 is still supported as of the release of v1.4.5. However, MongoDB v3.4 has been End of Life by Mongo, so we recommend customers upgrade at their earliest convenience. Going forward, when our shipped version of MongoDB is upgrade, we will continue to support the prior version of MongoDB, but deprecate the version before that. As an example, when the shipped version of MongoDB is upgrade to v4.0, we will continue to support v3.6 and deprecate v3.4. We estimate that this will require two MongoDB upgrades per year, which should not force our Enterprise Docker Platform users to upgrade their MongoDB image more than once a year.
Parent topic: Welcome