Get previously deployed values - AWS (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> 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.
- 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.
- See: /wiki/spaces/DRXXE/pages/6194875 at
Upgrade and Downgrade.
Parameters to check
Make sure the Helm chart is defined for aws 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: aws
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 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).