github.com/darkowlzz/helm@v2.5.1-0.20171213183701-6707fe0468d4+incompatible/docs/man/man1/helm_upgrade.1 (about)

     1  .TH "HELM" "1" "May 2017" "Auto generated by spf13/cobra" "" 
     2  .nh
     3  .ad l
     4  
     5  
     6  .SH NAME
     7  .PP
     8  helm\-upgrade \- upgrade a release
     9  
    10  
    11  .SH SYNOPSIS
    12  .PP
    13  \fBhelm upgrade [RELEASE] [CHART]\fP
    14  
    15  
    16  .SH DESCRIPTION
    17  .PP
    18  This command upgrades a release to a new version of a chart.
    19  
    20  .PP
    21  The upgrade arguments must be a release and chart. The chart
    22  argument can be either: a chart reference('stable/mariadb'), a path to a chart directory,
    23  a packaged chart, or a fully qualified URL. For chart references, the latest
    24  version will be specified unless the '\-\-version' flag is set.
    25  
    26  .PP
    27  To override values in a chart, use either the '\-\-values' flag and pass in a file
    28  or use the '\-\-set' flag and pass configuration from the command line.
    29  
    30  .PP
    31  You can specify the '\-\-values'/'\-f' flag multiple times. The priority will be given to the
    32  last (right\-most) file specified. For example, if both myvalues.yaml and override.yaml
    33  contained a key called 'Test', the value set in override.yaml would take precedence:
    34  
    35  .PP
    36  .RS
    37  
    38  .nf
    39  $ helm upgrade \-f myvalues.yaml \-f override.yaml redis ./redis
    40  
    41  .fi
    42  .RE
    43  
    44  .PP
    45  You can specify the '\-\-set' flag multiple times. The priority will be given to the
    46  last (right\-most) set specified. For example, if both 'bar' and 'newbar' values are
    47  set for a key called 'foo', the 'newbar' value would take precedence:
    48  
    49  .PP
    50  .RS
    51  
    52  .nf
    53  $ helm upgrade \-\-set foo=bar \-\-set foo=newbar redis ./redis
    54  
    55  .fi
    56  .RE
    57  
    58  
    59  .SH OPTIONS
    60  .PP
    61  \fB\-\-ca\-file\fP=""
    62      verify certificates of HTTPS\-enabled servers using this CA bundle
    63  
    64  .PP
    65  \fB\-\-cert\-file\fP=""
    66      identify HTTPS client using this SSL certificate file
    67  
    68  .PP
    69  \fB\-\-devel\fP[=false]
    70      use development versions, too. Equivalent to version '>0.0.0\-a'. If \-\-version is set, this is ignored.
    71  
    72  .PP
    73  \fB\-\-dry\-run\fP[=false]
    74      simulate an upgrade
    75  
    76  .PP
    77  \fB\-\-force\fP[=false]
    78      force resource update through delete/recreate if needed
    79  
    80  .PP
    81  \fB\-i\fP, \fB\-\-install\fP[=false]
    82      if a release by this name doesn't already exist, run an install
    83  
    84  .PP
    85  \fB\-\-key\-file\fP=""
    86      identify HTTPS client using this SSL key file
    87  
    88  .PP
    89  \fB\-\-keyring\fP="~/.gnupg/pubring.gpg"
    90      path to the keyring that contains public signing keys
    91  
    92  .PP
    93  \fB\-\-namespace\fP="default"
    94      namespace to install the release into (only used if \-\-install is set)
    95  
    96  .PP
    97  \fB\-\-no\-hooks\fP[=false]
    98      disable pre/post upgrade hooks
    99  
   100  .PP
   101  \fB\-\-recreate\-pods\fP[=false]
   102      performs pods restart for the resource if applicable
   103  
   104  .PP
   105  \fB\-\-repo\fP=""
   106      chart repository url where to locate the requested chart
   107  
   108  .PP
   109  \fB\-\-reset\-values\fP[=false]
   110      when upgrading, reset the values to the ones built into the chart
   111  
   112  .PP
   113  \fB\-\-reuse\-values\fP[=false]
   114      when upgrading, reuse the last release's values, and merge in any new values. If '\-\-reset\-values' is specified, this is ignored.
   115  
   116  .PP
   117  \fB\-\-set\fP=[]
   118      set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
   119  
   120  .PP
   121  \fB\-\-timeout\fP=300
   122      time in seconds to wait for any individual kubernetes operation (like Jobs for hooks)
   123  
   124  .PP
   125  \fB\-\-tls\fP[=false]
   126      enable TLS for request
   127  
   128  .PP
   129  \fB\-\-tls\-ca\-cert\fP="$HELM\_HOME/ca.pem"
   130      path to TLS CA certificate file
   131  
   132  .PP
   133  \fB\-\-tls\-cert\fP="$HELM\_HOME/cert.pem"
   134      path to TLS certificate file
   135  
   136  .PP
   137  \fB\-\-tls\-key\fP="$HELM\_HOME/key.pem"
   138      path to TLS key file
   139  
   140  .PP
   141  \fB\-\-tls\-verify\fP[=false]
   142      enable TLS for request and verify remote
   143  
   144  .PP
   145  \fB\-f\fP, \fB\-\-values\fP=[]
   146      specify values in a YAML file or a URL(can specify multiple)
   147  
   148  .PP
   149  \fB\-\-verify\fP[=false]
   150      verify the provenance of the chart before upgrading
   151  
   152  .PP
   153  \fB\-\-version\fP=""
   154      specify the exact chart version to use. If this is not specified, the latest version is used
   155  
   156  .PP
   157  \fB\-\-wait\fP[=false]
   158      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
   159  
   160  
   161  .SH OPTIONS INHERITED FROM PARENT COMMANDS
   162  .PP
   163  \fB\-\-debug\fP[=false]
   164      enable verbose output
   165  
   166  .PP
   167  \fB\-\-home\fP="~/.helm"
   168      location of your Helm config. Overrides $HELM\_HOME
   169  
   170  .PP
   171  \fB\-\-host\fP="localhost:44134"
   172      address of tiller. Overrides $HELM\_HOST
   173  
   174  .PP
   175  \fB\-\-kube\-context\fP=""
   176      name of the kubeconfig context to use
   177  
   178  .PP
   179  \fB\-\-tiller\-namespace\fP="kube\-system"
   180      namespace of tiller
   181  
   182  
   183  .SH SEE ALSO
   184  .PP
   185  \fBhelm(1)\fP
   186  
   187  
   188  .SH HISTORY
   189  .PP
   190  19\-May\-2017 Auto generated by spf13/cobra