Upgrade - OpenShift (4.2)

Owned by Jenni Wallin
Jun 03, 2024
4 min read

Upgrade Usage Engine

  1. Validate the Helm Chart Contents

    To ensure there are no errors in the Helm chart content, you can run the following:

    $ helm lint usage-engine-private-edition


    You can also run the helm template chart to see the yaml file with modified values:

    $ helm template usage-engine-private-edition

  2. Upgrade all pods.

    - Use the new License Key for the upgrade. In case you have not received a new License Key, see the Release Note for the alternative method.

    - In the case the upgrade fails, it will rollback automatically. The new resources from the upgrade will be removed automatically.

    Before you upgrade, validate the helm chart with a dry-run: Note that <release_platform> is the unique names that was defined at the installation. $ helm upgrade <release_platform> usage-engine-private-edition --set-file licenseKey=<licensekey_file> --dry-run --debug --namespace <namespace> If the validation is ok, continue with the upgrade: $ helm upgrade <release_platform> usage-engine-private-edition --set-file licenseKey=<licensekey_file> --atomic --cleanup-on-fail --debug --namespace <namespace>

  3. Verify the installation. STATUS Running. The READY state (ready/desired) should be 1/1, 2/2 and so on.  It can can take a few minutes before everything is in up and running.

Note!

The output will show the exposed ports when you run kubectl get services -n <namespace>. The exposed ports must be used instead of the ports 443, 9000, 6790, 80 and 9999

when you connect to the Desktop.

Manual Downgrade

If you need to do a manual downgrade of the system, see for more information.

Manual ECD rolling update

If Automatic Rolling Update was never defined for the ECDs, you need to manually upgrade the ECDs to the new image by clicking Upgrade in Desktop Online.

  1. Login to Desktop Online, see

  2. Click on Upgrade for the ECDs with a warning sign, to apply the upgrades.