github.com/valdemarpavesi/helm@v2.9.1+incompatible/docs/helm/helm_install.md (about) 1 ## helm install 2 3 install a chart archive 4 5 ### Synopsis 6 7 8 9 This command installs a chart archive. 10 11 The install argument must be a chart reference, a path to a packaged chart, 12 a path to an unpacked chart directory or a URL. 13 14 To override values in a chart, use either the '--values' flag and pass in a file 15 or use the '--set' flag and pass configuration from the command line, to force 16 a string value use '--set-string'. 17 18 $ helm install -f myvalues.yaml ./redis 19 20 or 21 22 $ helm install --set name=prod ./redis 23 24 or 25 26 $ helm install --set-string long_int=1234567890 ./redis 27 28 You can specify the '--values'/'-f' flag multiple times. The priority will be given to the 29 last (right-most) file specified. For example, if both myvalues.yaml and override.yaml 30 contained a key called 'Test', the value set in override.yaml would take precedence: 31 32 $ helm install -f myvalues.yaml -f override.yaml ./redis 33 34 You can specify the '--set' flag multiple times. The priority will be given to the 35 last (right-most) set specified. For example, if both 'bar' and 'newbar' values are 36 set for a key called 'foo', the 'newbar' value would take precedence: 37 38 $ helm install --set foo=bar --set foo=newbar ./redis 39 40 41 To check the generated manifests of a release without installing the chart, 42 the '--debug' and '--dry-run' flags can be combined. This will still require a 43 round-trip to the Tiller server. 44 45 If --verify is set, the chart MUST have a provenance file, and the provenance 46 file MUST pass all verification steps. 47 48 There are five different ways you can express the chart you want to install: 49 50 1. By chart reference: helm install stable/mariadb 51 2. By path to a packaged chart: helm install ./nginx-1.2.3.tgz 52 3. By path to an unpacked chart directory: helm install ./nginx 53 4. By absolute URL: helm install https://example.com/charts/nginx-1.2.3.tgz 54 5. By chart reference and repo url: helm install --repo https://example.com/charts/ nginx 55 56 CHART REFERENCES 57 58 A chart reference is a convenient way of reference a chart in a chart repository. 59 60 When you use a chart reference with a repo prefix ('stable/mariadb'), Helm will look in the local 61 configuration for a chart repository named 'stable', and will then look for a 62 chart in that repository whose name is 'mariadb'. It will install the latest 63 version of that chart unless you also supply a version number with the 64 '--version' flag. 65 66 To see the list of chart repositories, use 'helm repo list'. To search for 67 charts in a repository, use 'helm search'. 68 69 70 ``` 71 helm install [CHART] 72 ``` 73 74 ### Options 75 76 ``` 77 --ca-file string verify certificates of HTTPS-enabled servers using this CA bundle 78 --cert-file string identify HTTPS client using this SSL certificate file 79 --dep-up run helm dependency update before installing the chart 80 --devel use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored. 81 --dry-run simulate an install 82 --key-file string identify HTTPS client using this SSL key file 83 --keyring string location of public keys used for verification (default "~/.gnupg/pubring.gpg") 84 -n, --name string release name. If unspecified, it will autogenerate one for you 85 --name-template string specify template used to name the release 86 --namespace string namespace to install the release into. Defaults to the current kube config namespace. 87 --no-hooks prevent hooks from running during install 88 --password string chart repository password where to locate the requested chart 89 --replace re-use the given name, even if that name is already used. This is unsafe in production 90 --repo string chart repository url where to locate the requested chart 91 --set stringArray set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2) 92 --set-string stringArray set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2) 93 --timeout int time in seconds to wait for any individual Kubernetes operation (like Jobs for hooks) (default 300) 94 --tls enable TLS for request 95 --tls-ca-cert string path to TLS CA certificate file (default "$HELM_HOME/ca.pem") 96 --tls-cert string path to TLS certificate file (default "$HELM_HOME/cert.pem") 97 --tls-key string path to TLS key file (default "$HELM_HOME/key.pem") 98 --tls-verify enable TLS for request and verify remote 99 --username string chart repository username where to locate the requested chart 100 -f, --values valueFiles specify values in a YAML file or a URL(can specify multiple) (default []) 101 --verify verify the package before installing it 102 --version string specify the exact chart version to install. If this is not specified, the latest version is installed 103 --wait 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 104 ``` 105 106 ### Options inherited from parent commands 107 108 ``` 109 --debug enable verbose output 110 --home string location of your Helm config. Overrides $HELM_HOME (default "~/.helm") 111 --host string address of Tiller. Overrides $HELM_HOST 112 --kube-context string name of the kubeconfig context to use 113 --tiller-connection-timeout int the duration (in seconds) Helm will wait to establish a connection to tiller (default 300) 114 --tiller-namespace string namespace of Tiller (default "kube-system") 115 ``` 116 117 ### SEE ALSO 118 * [helm](helm.md) - The Helm package manager for Kubernetes. 119 120 ###### Auto generated by spf13/cobra on 20-Mar-2018