to the running installation, the config file for the new installation should be prepared

by following these steps:

1. Retrieve the values.yaml

1. file that you have used previously, or if you

1. want to start from scratch, you

1. extract it from the installation by

1. running these commands:

   Code Block
   helm -n <namespace> get all <helm name>

1. E.g: helm -n uepe get all uepe

1. Where

1. uepe is the helm name

1. you have selected for your installation. You will see list similar to the one below.

   Code Block
   helm list NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION external-dns uepe 1 2024-05-08 15:27:48.258978207 +0200 CEST deployed external-dns-7.2.0 0.14.1 ingress-nginx uepe 1 2024-05-08 16:18:43.919980224 +0200 CEST deployed ingress-nginx-4.10.0 1.10.0 uepe uepe 3 2024-05-10 14:16:17.724426589 +0200 CEST deployed usage-engine-private-edition-4.0.0 4.0.0

1. Extract the values manually from the output. Copy the lines below “USER-SUPPLIED VALUES:” and stop at the blank line before “COMPUTED VALUES:”. Save the copied content to the config file valuesFromSystem.yaml.

2. Update helm repository to get the latest helm chart versions by running the following command.

   Code Block
   helm repo list helm repo update

3. Retrieve the new version from the repository

1. by running the following command. Refer to Release Information for the Helm Chart version.

   Code Block
   helm fetch <repo name>/usage-engine-private-edition --version <version> --untar

1. For example:

   Code Block
   helm fetch digitalroute/usage-engine-private-edition --version 4.0.0 --untar

2. Next, check the file CHANGELOG.md inside the created folder to find out what may have changed in the new version when it comes to the values-file.
   

1. If you are uncertain about how to interpret the

1. content of the file,

1. see below for some examples of keys and how to interpret them:

   Code Block
   The following values have been removed: * ```mzOperator.clusterWide``` * ```mzOperator.experimental.performPeriodicWorkflowCleanup``` * ```jmx.remote``` * ```platform.debug.jmx```

1. means that in the values file they

1. should be entered as:

   Code Block
   mzOperator: clusterWide: experimental: performPeriodicWorkflowCleanup jmx: remote: platform: debug: jmx:

   Each part of the key

1. does not necessarily follow

1. directly after the previous one, but always before any other “parent” on the same level. So

1. in this example

1. of a values.yaml file:

   Code Block
   debug: script: enabled: false log: level: codeserver: info jetty: 'off' others: warn

1. an example of a key could be

1. debug.log.level.

1. jetty.

2. Make any necessary updates based on changed field you may be using in the

1. valuesFromSystem.yaml file you got from the existing installation so it matches the new version.

2. Take note of any fields that have been deprecated or removed since the last version

1. so any configuration of those fields can be replaced.

8. When you have updated the valuesFromSystem.yaml file you can test it

8. by running this command:

helm upgrade --install uepe digitalroute/usage-engine-private-edition --atomic --cleanup-on-fail --version 4.0.0 -n uepe -f 

valuesFromSystem.yaml --dry-run=server