LinuxCommandLibrary
GitHubF-DroidGoogle Play Store

helm-upgrade

Upgrade a Helm release to a new chart version or a new set of values

TLDR

Upgrade a release to the latest chart from a repository
$ helm upgrade [release] [repo]/[chart]
copy
Upgrade from an unpacked chart directory
$ helm upgrade [release] [path/to/chart]
copy
Upgrade, or install if the release does not exist yet
$ helm upgrade -i [release] [repo]/[chart]
copy
Pin a chart version
$ helm upgrade [release] [repo]/[chart] --version [1.2.3]
copy
Upgrade in a namespace
$ helm upgrade [release] [repo]/[chart] -n [namespace]
copy
Pass a values file
$ helm upgrade [release] [repo]/[chart] -f [values.yaml]
copy
Override one value on the command line
$ helm upgrade [release] [repo]/[chart] --set [key]=[value]
copy
Simulate on the client, without talking to the cluster
$ helm upgrade [release] [repo]/[chart] --dry-run=client
copy

SYNOPSIS

helm upgrade [RELEASE] [CHART] [flags]

DESCRIPTION

helm upgrade replaces an existing release with a new revision of a chart, or with new values for the same chart. The chart argument is a repo/name reference, a directory, a packaged chart, or a URL.This is a subcommand of helm, not a separate program. Helm keeps the old revision so helm rollback can return to it, up to --history-max.Later -f and --set arguments override earlier ones when the same key is set twice.

PARAMETERS

-i, --install

Install the release when no release of that name exists.
--version constraint
Chart version to use. A tag such as 1.2.3, or a range such as ^2.0.0. Without this flag Helm uses the latest version.
-n, --namespace namespace
Namespace of the release.
--create-namespace
With --install, create the namespace if it is missing.
-f, --values file
Values from a YAML file or a URL. Repeat the flag to merge several files. The right-most file wins on duplicate keys.
--set key=value
Set a value from the command line. Repeat the flag, or separate pairs with commas. The right-most setting wins.
--reuse-values
Keep the previous release's values and merge in --set and -f. Ignored when --reset-values is also set.
--reset-values
Drop the previous values and use the chart defaults, plus any --set and -f overrides.
--dry-run=none | client | server
none (the default) performs the upgrade. client renders manifests locally and does not contact the cluster. server renders on the cluster without persisting the release. A dry run prints Secrets. Add --hide-secret to omit them.
--timeout duration
How long to wait for one Kubernetes operation. Default 5m0s.
--wait[=watcher | hookOnly | legacy]
Wait until resources are ready, up to --timeout. The flag alone means watcher. If the flag is omitted, the strategy is hookOnly.
--rollback-on-failure
Roll back to the last successful release if the upgrade fails. This defaults --wait to watcher.
--history-max count
How many revisions to keep. 0 means no limit. Default 10.

INSTALL

sudo dnf install helm
copy
sudo pacman -S helm
copy
sudo apk add helm
copy
sudo zypper install helm
copy
brew install helm
copy
nix profile install nixpkgs#helm
copy

CAVEATS

On Helm 4, --dry-run is not a boolean. The default value none runs the upgrade for real. Pass --dry-run=client or --dry-run=server to simulate.--reuse-values and --reset-values disagree with each other. --reset-values wins. --reset-then-reuse-values is a third mode: chart defaults, then the last release's values, then the flags on this command. It is ignored if either of the other two is set.

SEE ALSO

RESOURCES

Copied to clipboard
Kai