.TH "HELM" "1" "Apr 2017" "Auto generated by spf13/cobra" "" 
.nh
.ad l


.SH NAME
.PP
helm\-upgrade \- upgrade a release


.SH SYNOPSIS
.PP
\fBhelm upgrade [RELEASE] [CHART]\fP


.SH DESCRIPTION
.PP
This command upgrades a release to a new version of a chart.

.PP
The upgrade arguments must be a release and chart. The chart
argument can be either: a chart reference('stable/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.

.PP
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.

.PP
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:

.PP
.RS

.nf
$ helm upgrade \-f myvalues.yaml \-f override.yaml redis ./redis

.fi
.RE

.PP
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:

.PP
.RS

.nf
$ helm upgrade \-\-set foo=bar \-\-set foo=newbar redis ./redis

.fi
.RE


.SH OPTIONS
.PP
\fB\-\-dry\-run\fP[=false]
    simulate an upgrade

.PP
\fB\-i\fP, \fB\-\-install\fP[=false]
    if a release by this name doesn't already exist, run an install

.PP
\fB\-\-keyring\fP="~/.gnupg/pubring.gpg"
    path to the keyring that contains public signing keys

.PP
\fB\-\-namespace\fP="default"
    namespace to install the release into (only used if \-\-install is set)

.PP
\fB\-\-no\-hooks\fP[=false]
    disable pre/post upgrade hooks

.PP
\fB\-\-recreate\-pods\fP[=false]
    performs pods restart for the resource if applicable

.PP
\fB\-\-reset\-values\fP[=false]
    when upgrading, reset the values to the ones built into the chart

.PP
\fB\-\-reuse\-values\fP[=false]
    when upgrading, reuse the last release's values, and merge in any new values. If '\-\-reset\-values' is specified, this is ignored.

.PP
\fB\-\-set\fP=[]
    set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)

.PP
\fB\-\-timeout\fP=300
    time in seconds to wait for any individual kubernetes operation (like Jobs for hooks)

.PP
\fB\-\-tls\fP[=false]
    enable TLS for request

.PP
\fB\-\-tls\-ca\-cert\fP="$HELM\_HOME/ca.pem"
    path to TLS CA certificate file

.PP
\fB\-\-tls\-cert\fP="$HELM\_HOME/cert.pem"
    path to TLS certificate file

.PP
\fB\-\-tls\-key\fP="$HELM\_HOME/key.pem"
    path to TLS key file

.PP
\fB\-\-tls\-verify\fP[=false]
    enable TLS for request and verify remote

.PP
\fB\-f\fP, \fB\-\-values\fP=[]
    specify values in a YAML file (can specify multiple)

.PP
\fB\-\-verify\fP[=false]
    verify the provenance of the chart before upgrading

.PP
\fB\-\-version\fP=""
    specify the exact chart version to use. If this is not specified, the latest version is used

.PP
\fB\-\-wait\fP[=false]
    if set, will wait until all Pods, PVCs, Services, and minimum number of Pods of a Deployment are in a ready state before marking the release as successful. It will wait for as long as \-\-timeout


.SH OPTIONS INHERITED FROM PARENT COMMANDS
.PP
\fB\-\-debug\fP[=false]
    enable verbose output

.PP
\fB\-\-home\fP="~/.helm"
    location of your Helm config. Overrides $HELM\_HOME

.PP
\fB\-\-host\fP=""
    address of tiller. Overrides $HELM\_HOST

.PP
\fB\-\-kube\-context\fP=""
    name of the kubeconfig context to use

.PP
\fB\-\-tiller\-namespace\fP="kube\-system"
    namespace of tiller


.SH SEE ALSO
.PP
\fBhelm(1)\fP


.SH HISTORY
.PP
12\-Apr\-2017 Auto generated by spf13/cobra