helm upgrade

Upgrade a release

Options

NameDescription
--atomicIf set, upgrade process rolls back changes made in case of failed upgrade. The --wait flag will be set automatically if --atomic is used
--ca-file <ca-file>Verify certificates of HTTPS-enabled servers using this CA bundle
--cert-file <cert-file>Identify HTTPS client using this SSL certificate file
--cleanup-on-failAllow deletion of new resources created in this upgrade when upgrade fails
--create-namespaceIf --install is set, create the release namespace if not present
--dependency-updateUpdate dependencies if they are missing before installing the chart
--description <description>Add a custom description
--develUse development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored
--disable-openapi-validationIf set, the upgrade process will not validate rendered templates against the Kubernetes OpenAPI Schema
--dry-runSimulate an upgrade
--forceForce resource updates through a replacement strategy
--history-max <history-max>Limit the maximum number of revisions saved per release. Use 0 for no limit
--insecure-skip-tls-verifySkip tls certificate checks for the chart download
--install, -iIf a release by this name doesn't already exist, run an install
--key-file <key-file>Identify HTTPS client using this SSL key file
--keyring <keyring>Location of public keys used for verification
--no-hooksDisable pre/post upgrade hooks
--output, -o <output>Prints the output in the specified format. Allowed values: table, json, yaml
--pass-credentialsPass credentials to all domains
--password <password>Chart repository password where to locate the requested chart
--post-renderer <post-renderer>The path to an executable to be used for post rendering. If it exists in $PATH, the binary will be used, otherwise it will try to look for the executable at the given path
--post-renderer-args <post-renderer-args>
  • Repeatable ♾
--recreate-podsPerforms pods restart for the resource if applicable
--render-subchart-notesIf set, render subchart notes along with the parent
--repo <repo>Chart repository url where to locate the requested chart
--reset-valuesWhen upgrading, reset the values to the ones built into the chart
--reuse-valuesWhen upgrading, reuse the last release's values and merge in any overrides from the command line via --set and -f. If '--reset-values' is specified, this is ignored
--set <set>
  • Repeatable ♾
--set-file <set-file>
  • Repeatable ♾
--set-string <set-string>
  • Repeatable ♾
--skip-crdsIf set, no CRDs will be installed when an upgrade is performed with install flag enabled. By default, CRDs are installed if not already present, when an upgrade is performed with install flag enabled
--timeout <timeout>Time to wait for any individual Kubernetes operation (like Jobs for hooks)
--username <username>Chart repository username where to locate the requested chart
--values, -f <values>
  • Repeatable ♾
--verifyVerify the package before using it
--version <version>Specify a version constraint for the chart version to use. This constraint can be a specific tag (e.g. 1.1.1) or it may reference a valid range (e.g. ^2.0.0). If this is not specified, the latest version is used
--waitIf set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a Deployment, StatefulSet, or ReplicaSet are in a ready state before marking the release as successful. It will wait for as long as --timeout
--wait-for-jobsIf set and --wait enabled, will wait until all Jobs have been completed before marking the release as successful. It will wait for as long as --timeout