Versions Compared

Old Version 4

changes.mady.by.user Jenni Wallin

Saved on

compared with

New Version 5

changes.mady.by.user Jenni Wallin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Validate the Helm Chart Contents

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

    Code Block
    $ helm lint usage-engine-private-edition


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

    Code Block
    $ 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.

    Code Block
    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.

    Code Block
    # Verify pods

$ kubectl get pods --namespace <namespace>

#Example
NAME                                              READY   STATUS    RESTARTS   AGE
uepe-operator-controller-manager-646b766d44-2s9sl 2/2     Running   0          154m
uepe-operator-controller-manager-646b766d44-mmzhs 2/2     Running   0          154m
desktop-online-7ff989968b-9hd2b                   1/1     Running   0          154m
platform-0                                        1/1     Running   0          154m

# Verify service contexts to connect

$ kubectl get services --namespace <namespace>

#Example
NAME                                             TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)                         AGE
uepe-operator-controller-manager-metrics-service ClusterIP   10.107.192.50    <none>        8443/TCP                        154m
uepe-operator-controller-manager-service         ClusterIP   10.100.197.208   <none>        443/TCP                         154m
desktop-online                                   NodePort    10.101.65.181    <none>        80:31200/TCP,443:31300/TCP      154m
platform                                         NodePort    10.96.40.10      <none>        9000:31600/TCP,6790:31700/TCP   154m
Note

...

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

...

.

Note

...

Manual Downgrade

In the case you need to do a manual downgrade of the system, see Downgrade(

...

4.0).

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 in Desktop Online by clicking Upgrade in the EC deployment interface.

...