Get previously deployed values - Private Cloud (3.1)

View previously deployed values

In this example we save the values in file:  platform_values.txt.

Check so that your namespace is available.
$ helm list --namespace <namespace>

Example:
$ helm list --namespace user1
NAME   	NAMESPACE	REVISION	UPDATED                                 	STATUS  	CHART                                                 	APP VERSION
platpod user1    	2       	2020-09-01 14:57:55.458292074 +0200 CEST	deployed	usage-engine-private-edition-10.1.0-release-20200824070905.1566f6c   	10.1.0     

Save the installed values to a file, in the case you need them later in the upgrade.
$ helm get values <release_platform> -a --namespace <namespace> > platform_values.txt

Editing the new values.yaml file

View the contents of the installed values.yaml file. Either if you have access to the already installed values.yaml file or look at the platform_values.txt file explained above:

  • cat <current installation> usage-engine-private-edition / values.yaml

Edit and update the new installation's values.yaml file with the site unique values, that you find in the installed values.yaml file.

  • Do NOT change the image tags in the new values.yaml file.

Check the Release Notes for any special considerations concerning the new values.yaml file. Update them accordingly.

Parameters to check

  1. Make sure the Helm chart is defined for on-premise (Private cloud) by viewing the file: usage-engine-private-edition / values.yaml

    $ cat usage-engine-private-edition/values.yaml | grep environment:
    
    # Only on-premise and aws supported for now
    environment: on-premise
  2. Make sure the new tags are pointing at the new image by viewing the file: usage-engine-private-edition / values.yaml

    $ cat usage-engine-private-edition/values.yaml | grep tag:


Persistent Storage is required for a possible downgrade

To be prepared for a possible downgrade later, make sure that you have defined Persistent Storage prior to the upgrade. Persistent Storage is mandatory to be able to perform a downgrade.

For information about Persistent Storage, see Persistent Storage (3.0).