Upgrading to AC v4.2
This section discusses how you can upgrade from AC v4.1 to AC v4.2 or AC v4.2.x.
Possible upgrade path
If you are upgrading to AC v4.2 or v4.2.x, refer to the following table for possible upgrade path.
| Old version | New version |
|---|---|
| v4.1.6 | v4.2 |
| v4.2 | v4.2.2 |
| v4.2.2 | 4.2.3 |
| 4.2.3 | 4.2.4 |
| 4.2.4 | 4.2.5 |
| 4.2.5 | 4.2.6 |
| 4.2.6 | 4.2.7 |
Prerequisites
- Take the backup of all the configuration files present in shared/ folder, for example, truststore, keystore, kerberos config, etc. before upgrading. This backup will help you restore the entries you may have made before upgrading.
- Deactivate the dedicated Deployments (runtime).
- Deploy the Roles package.
Download the global values.yaml file available on Artifact Hub page for AC v4.2.x by using the DEFAULT VALUES option on it, and configure it based on your requirement.
Important
While configuring the values.yaml file, ensure that you have the same tags for all the microservices.
Ensure that you select the appropriate chart version (based on which version you are upgrading to) in the CHART VERSIONS section on Artifact Hub page before you download the values.yaml file.
- If you want to use Kubernetes Event-driven Autoscaling for microservices pod autoscaling purposes, deploy KEDA on your Kubernetes Cluster.
To ensure that the application starts running successfully after its deployment, you need to set the property EXECUTE_STATIC_JOB in the static section of the global values.yaml file.
Property
Description
EXECUTE_STATIC_JOB Set the value for this property to true to ensure that the files required for running the application are copied in the PVC while deploying the application.
Steps to upgrade to AC 4.2
You can upgrade to AC v4.2 AC v4.2.x of Adeptia Connect by following the steps in the same order as given below.
- Update the Helm repository
- Upgrade to the next version
Updating the Helm Repository
Before you start to move to next version, make sure that you have updated the Helm Repository.
To update the Helm Repository, run the following command on the Helm CLI.
helm repo update
Upgrading to the higher version
After you've updated the Helm Repository, run the following command on the Helm CLI.
helm upgrade -i my-adeptia-connect adeptia-connect/adeptia-connect --version <Version> -f adeptia/values.yaml -n < NAMESPACE >
where,
- my-adeptia-connect is the name of the release.
adeptia-connect/adeptia-connect is path of the application helm repository.
<Version> is the version of Adeptia Connect that you want to install.
Important
Use a specific version number in the version argument, else the latest version of Adeptia Connect will be installed.- -f denotes file.
- adeptia/values.yaml is the location of your values.yaml file.
- -n denotes namespace.
- <NAMESPACE> is the namespace in the Kubernetes Cluster to which the application belongs.
Post upgrade steps
Once you have finished upgrading, follow the steps given below:
- Activate the dedicated Deployments (runtime) that you had deactivated before the upgrade.
- Update the configuration files with the changes you may have made in any of them before upgrade. Use the backed up configuration files to ascertain the changes.
- Edit any existing provider and replace the uploaded jars with activemq-core-5.7.0.jar, and geronimo-j2ee-management_1.1_spec-1.0.1.jar files for the provider to work. For more details, refer to this page.