...

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:

   Code Block
   $ helm lint usage-engine-private-

...

1. editionYou 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: $ helm upgrade <release_name_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_name_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 aws-alb-ingress-controller-5fbf5b59d9-wsgzt 1/1 Running 0 24h efs-provisioner-69854b5db8-2bhds 1/1 Running 0 24h external-dns-7b79999d56-tq6pl 1/1 Running 0 24h mz-ingress-nginx-5767cbbcf8-d6crt 1/1 Running 0 24h mz-operator-controller-manager-0 2/2 Running 0 24h mzonline-574cb89f54-7vkrg 1/1 Running 0 24h platform-0 1/1 Running 0 24h

...

...

1. # Verify service contexts to connect $ kubectl get services --namespace <namespace> #Example NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE external-dns ClusterIP 10.100.125.15 <none> 7979/TCP 24h ingress-nginx NodePort 10.100.31.226 <none> 80:32266/TCP,443:30403/TCP 24h kubernetes ClusterIP 10.100.0.1 <none> 443/TCP 46h mz-operator-controller-manager-metrics-service ClusterIP 10.100.152.116 <none> 8443/TCP 24h mz-operator-controller-manager-service ClusterIP 10.100.207.9 <none> 443/TCP 24h mzonline NodePort 10.100.8.213 <none> 80:31250/TCP,443:30738/TCP 24h platform LoadBalancer 10.100.30.233 a21e6b94b01a0f02fe62803350-284407273.eu-west-1.elb.amazonaws.com 9000:31561/TCP,6790:31654/TCP,443:31216

...

1. /TCP

...

1. 24h

   Note
   title Note!
   The output will show the exposed ports when you run kubectl get services. We have used a default namespace and helm chart for efs-provisioner,  external-dns and aws-alb-ingress-controller from 3PP → "Readme" instruction from zip file in /wiki/spaces/DRXXE/pages/6194875

   
   

...

...

...

Manual ECD rolling update

• In

  the

  case Automatic Rolling Update was never defined for the ECDs, you need to enter the Web interface and manually upgrade the ECDs to the new image by clicking Upgrade in the EC deployment interface.

1. Connect to the Web Interface:

   Info
   title Web-Interface
   Code Block Web interface: https://mzonline.<domain>/ Example: https://mzonline.mz-eks.tafdr.net/

2. Login to the Web Interface and click on Upgrade for the ECDs with a warning sign, to apply the upgrades.

...

1. Image Added

...

1. Image Added

   
   Example of the ECD ecd01, with a warning sign ready for the image upgrade.