github.com/sgoings/helm@v2.0.0-alpha.2.0.20170406211108-734e92851ac3+incompatible/docs/man/man1/helm_upgrade.1 (about) 1 .TH "HELM" "1" "Mar 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\-\-dry\-run\fP[=false] 62 simulate an upgrade 63 64 .PP 65 \fB\-i\fP, \fB\-\-install\fP[=false] 66 if a release by this name doesn't already exist, run an install 67 68 .PP 69 \fB\-\-keyring\fP="~/.gnupg/pubring.gpg" 70 path to the keyring that contains public signing keys 71 72 .PP 73 \fB\-\-namespace\fP="default" 74 namespace to install the release into (only used if \-\-install is set) 75 76 .PP 77 \fB\-\-no\-hooks\fP[=false] 78 disable pre/post upgrade hooks 79 80 .PP 81 \fB\-\-recreate\-pods\fP[=false] 82 performs pods restart for the resource if applicable 83 84 .PP 85 \fB\-\-reset\-values\fP[=false] 86 when upgrading, reset the values to the ones built into the chart 87 88 .PP 89 \fB\-\-set\fP=[] 90 set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2) 91 92 .PP 93 \fB\-\-timeout\fP=300 94 time in seconds to wait for any individual kubernetes operation (like Jobs for hooks) 95 96 .PP 97 \fB\-f\fP, \fB\-\-values\fP=[] 98 specify values in a YAML file (can specify multiple) 99 100 .PP 101 \fB\-\-verify\fP[=false] 102 verify the provenance of the chart before upgrading 103 104 .PP 105 \fB\-\-version\fP="" 106 specify the exact chart version to use. If this is not specified, the latest version is used 107 108 .PP 109 \fB\-\-wait\fP[=false] 110 if set, will wait until all Pods, PVCs, and Services are in a ready state before marking the release as successful. It will wait for as long as \-\-timeout 111 112 113 .SH OPTIONS INHERITED FROM PARENT COMMANDS 114 .PP 115 \fB\-\-debug\fP[=false] 116 enable verbose output 117 118 .PP 119 \fB\-\-home\fP="~/.helm" 120 location of your Helm config. Overrides $HELM\_HOME 121 122 .PP 123 \fB\-\-host\fP="" 124 address of tiller. Overrides $HELM\_HOST 125 126 .PP 127 \fB\-\-kube\-context\fP="" 128 name of the kubeconfig context to use 129 130 .PP 131 \fB\-\-tiller\-namespace\fP="kube\-system" 132 namespace of tiller 133 134 135 .SH SEE ALSO 136 .PP 137 \fBhelm(1)\fP 138 139 140 .SH HISTORY 141 .PP 142 11\-Mar\-2017 Auto generated by spf13/cobra