Skip to content

Commit

Permalink
docs: add an example for using the upgrade command with existing values
Browse files Browse the repository at this point in the history
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 protected]>
  • Loading branch information
josegonzalez authored Jun 3, 2023
1 parent 1c4885f commit e35bf1f
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions cmd/helm/upgrade.go
Original file line number Diff line number Diff line change
Expand Up @@ -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 {
Expand Down

0 comments on commit e35bf1f

Please sign in to comment.