Helm Upgrade

helm upgrade

upgrade a release

Synopsis

This command upgrades a release to a new version of a chart.

The upgrade arguments must be a release and chart. The chart argument can be either: a chart reference(‘example/mariadb’), a path to a chart directory, a packaged chart, or a fully qualified URL. For chart references, the latest version will be specified unless the ‘—version’ flag is set.

To override values in a chart, use either the ‘—values’ flag and pass in a file or use the ‘—set’ flag and pass configuration from the command line, to force string values, use ‘—set-string’. You can use ‘—set-file’ to set individual values from a file when the value itself is too long for the command line or is dynamically generated.

You can specify the ‘—values’/‘-f’ flag multiple times. The priority will be given to the last (right-most) file specified. For example, if both myvalues.yaml and override.yaml contained a key called ‘Test’, the value set in override.yaml would take precedence:

  1. $ helm upgrade -f myvalues.yaml -f override.yaml redis ./redis

You can specify the ‘—set’ flag multiple times. The priority will be given to the last (right-most) set specified. For example, if both ‘bar’ and ‘newbar’ values are set for a key called ‘foo’, the ‘newbar’ value would take precedence:

  1. $ helm upgrade --set foo=bar --set foo=newbar redis ./redis
  1. helm upgrade [RELEASE] [CHART] [flags]

Options

  1. --atomic if set, upgrade process rolls back changes made in case of failed upgrade. The --wait flag will be set automatically if --atomic is used
  2. --ca-file string verify certificates of HTTPS-enabled servers using this CA bundle
  3. --cert-file string identify HTTPS client using this SSL certificate file
  4. --cleanup-on-fail allow deletion of new resources created in this upgrade when upgrade fails
  5. --create-namespace if --install is set, create the release namespace if not present
  6. --dependency-update update dependencies if they are missing before installing the chart
  7. --description string add a custom description
  8. --devel use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored
  9. --disable-openapi-validation if set, the upgrade process will not validate rendered templates against the Kubernetes OpenAPI Schema
  10. --dry-run simulate an upgrade
  11. --force force resource updates through a replacement strategy
  12. -h, --help help for upgrade
  13. --history-max int limit the maximum number of revisions saved per release. Use 0 for no limit (default 10)
  14. --insecure-skip-tls-verify skip tls certificate checks for the chart download
  15. -i, --install if a release by this name doesn't already exist, run an install
  16. --key-file string identify HTTPS client using this SSL key file
  17. --keyring string location of public keys used for verification (default "~/.gnupg/pubring.gpg")
  18. --no-hooks disable pre/post upgrade hooks
  19. -o, --output format prints the output in the specified format. Allowed values: table, json, yaml (default table)
  20. --pass-credentials pass credentials to all domains
  21. --password string chart repository password where to locate the requested chart
  22. --post-renderer postRendererString 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
  23. --post-renderer-args postRendererArgsSlice an argument to the post-renderer (can specify multiple) (default [])
  24. --render-subchart-notes if set, render subchart notes along with the parent
  25. --repo string chart repository url where to locate the requested chart
  26. --reset-values when upgrading, reset the values to the ones built into the chart
  27. --reuse-values when 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
  28. --set stringArray set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
  29. --set-file stringArray set values from respective files specified via the command line (can specify multiple or separate values with commas: key1=path1,key2=path2)
  30. --set-string stringArray set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
  31. --skip-crds if 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
  32. --timeout duration time to wait for any individual Kubernetes operation (like Jobs for hooks) (default 5m0s)
  33. --username string chart repository username where to locate the requested chart
  34. -f, --values strings specify values in a YAML file or a URL (can specify multiple)
  35. --verify verify the package before using it
  36. --version string 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
  37. --wait if 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
  38. --wait-for-jobs if 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

Options inherited from parent commands

  1. --debug enable verbose output
  2. --kube-apiserver string the address and the port for the Kubernetes API server
  3. --kube-as-group stringArray group to impersonate for the operation, this flag can be repeated to specify multiple groups.
  4. --kube-as-user string username to impersonate for the operation
  5. --kube-ca-file string the certificate authority file for the Kubernetes API server connection
  6. --kube-context string name of the kubeconfig context to use
  7. --kube-token string bearer token used for authentication
  8. --kubeconfig string path to the kubeconfig file
  9. -n, --namespace string namespace scope for this request
  10. --registry-config string path to the registry config file (default "~/.config/helm/registry/config.json")
  11. --repository-cache string path to the file containing cached repository indexes (default "~/.cache/helm/repository")
  12. --repository-config string path to the file containing repository names and URLs (default "~/.config/helm/repositories.yaml")

SEE ALSO

  • helm - The Helm package manager for Kubernetes.
Auto generated by spf13/cobra on 18-May-2022