Versions Compared

Version Old Version 3 New Version 4
Changes made by

David Sjölin

Jenni Wallin

Saved on

Key

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

Preparations

Before doing anything actively to the running installation, the config file for the new installation should be prepared .First, retrieve by following these steps:

  1. Retrieve the values.yaml

you’ve

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

don’t have it

  1. want to start from scratch, you

can get

  1. extract it from the installation by

doing this

  1. running these commands:

    Code Block
    helm get all <helm name> > <output filename>.yaml
E.g:
helm get all uepe > valuesFromSystem.yaml

    Where

“uepe”

  1. uepe is the helm name

you’ve chosen

  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
Next retrieve

  1. Retrieve the new version from the repository by running the following command:

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

  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.

In case you’re

  1. If you are uncertain about how to interpret the

format

  1. content of the file,

here are

  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```
The above mean

  1. means that in the values file they

are

  1. should be entered as:

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

    Each part of the key

doesn’t

  1. does not necessarily follow

immediately

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

on

  1. in this example

from

  1. of a values.yaml file:

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

  1. an example of a key could be

“debug

  1. debug.log.level.

jetty”

  1. jetty.

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

-

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

  2. TODO: What does the user do if we’ve removed something that they use?

  3. When

you’re update

  1. you have updated the values.yamle file you can test it

using

  1. by running this command:

Code Block
helm upgrade --install uepe digitalroute/usage-engine-private-edition --version 4.0.0 -n uepe -f fromHelm.yaml --dry-run=server

...