Versions Compared

Key

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

View previously deployed values

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

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

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

Note, If namespace is used, add this option to the commands: --namespace <namespace_name>

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.

...

Parameters to check

  1. Make sure the Helm chart is defined for aws by viewing the file: usage-engine-private-edition / values.yaml

    Code Block
    $ cat usage-engine-private-edition/values.yaml | grep environment:
    
    # Only on-premise and aws supported for now
    environment: aws


  2. Make sure the new tags are pointing at the new image by viewing the file: usage-engine-private-edition / values.yaml

    Code Block
    $ cat usage-engine-private-edition/values.yaml | grep tag:
    [hide]New Line[/hide]


Note
titlePersistent Storage 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).