docs: add an example for using the upgrade command with existing values

For users attempting to update a helm chart to add a missing config, it isn't totally clear how one should use helm upgrade.

Signed-off-by: Jose Diaz-Gonzalez <email@josediazgonzalez.com>
pull/12119/head
Jose Diaz-Gonzalez 1 year ago committed by GitHub
parent 1c4885fce7
commit e35bf1f939
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -65,6 +65,13 @@ last (right-most) set specified. For example, if both 'bar' and 'newbar' values
set for a key called 'foo', the 'newbar' value would take precedence:
$ helm upgrade --set foo=bar --set foo=newbar redis ./redis
You can update the values for an existing release with this command as well via the
'--reuse-values' flag. The 'RELEASE' and 'CHART' arguments should be set to the original
parameters, and existing values will be merged with any values set via '--values'/'-f'
or '--set' flags. Priority is given to new values.
$ helm upgrade --reuse-values --set foo=bar --set foo=newbar redis ./redis
`
func newUpgradeCmd(cfg *action.Configuration, out io.Writer) *cobra.Command {

Loading…
Cancel
Save