helm install

Install a chart archive

Synopsis

This command installs a chart archive.

The install argument must be a chart reference, a path to a packaged chart,a path to an unpacked chart directory or a URL.

To override values in a chart, use either the ‘–values’ flag and pass in a fileor use the ‘–set’ flag and pass configuration from the command line. To force stringvalues in ‘–set’, use ‘–set-string’ instead. In case a value is large and thereforeyou want not to use neither ‘–values’ nor ‘–set’, use ‘–set-file’ to read thesingle large value from file.

$ helm install -f myvalues.yaml ./redis

or

$ helm install --set name=prod ./redis

or

$ helm install --set-string long-int=1234567890 ./redis

or$ helm install –set-file multiline-text=path/to/textfile

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

$ helm install -f myvalues.yaml -f override.yaml ./redis

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

$ helm install --set foo=bar --set foo=newbar ./redis

To check the generated manifests of a release without installing the chart,the ‘–debug’ and ‘–dry-run’ flags can be combined. This will still require around-trip to the Tiller server.

If –verify is set, the chart MUST have a provenance file, and the provenancefile MUST pass all verification steps.

There are five different ways you can express the chart you want to install:

• By chart reference: helm install stable/mariadb
• By path to a packaged chart: helm install ./nginx-1.2.3.tgz
• By path to an unpacked chart directory: helm install ./nginx
• By absolute URL: helm install https://example.com/charts/nginx-1.2.3.tgz
• By chart reference and repo url: helm install –repo https://example.com/charts/ nginxCHART REFERENCES

A chart reference is a convenient way of reference a chart in a chart repository.

When you use a chart reference with a repo prefix (‘stable/mariadb’), Helm will look in the localconfiguration for a chart repository named ‘stable’, and will then look for achart in that repository whose name is ‘mariadb’. It will install the latestversion of that chart unless you also supply a version number with the‘–version’ flag.

To see the list of chart repositories, use ‘helm repo list’. To search forcharts in a repository, use ‘helm search’.

helm install [CHART] [flags]

Options

      --atomic                   If set, installation process purges chart on fail, also sets --wait flag
      --ca-file string           Verify certificates of HTTPS-enabled servers using this CA bundle
      --cert-file string         Identify HTTPS client using this SSL certificate file
      --dep-up                   Run helm dependency update before installing the chart
      --description string       Specify a description for the release
      --devel                    Use development versions, too. Equivalent to version '>0.0.0-0'. If --version is set, this is ignored.
      --dry-run                  Simulate an install
  -h, --help                     help for install
      --key-file string          Identify HTTPS client using this SSL key file
      --keyring string           Location of public keys used for verification (default "~/.gnupg/pubring.gpg")
  -n, --name string              The release name. If unspecified, it will autogenerate one for you
      --name-template string     Specify template used to name the release
      --namespace string         Namespace to install the release into. Defaults to the current kube config namespace.
      --no-crd-hook              Prevent CRD hooks from running, but run other hooks
      --no-hooks                 Prevent hooks from running during install
  -o, --output string            Prints the output in the specified format. Allowed values: table, json, yaml (default "table")
      --password string          Chart repository password where to locate the requested chart
      --render-subchart-notes    Render subchart notes along with the parent
      --replace                  Re-use the given name, even if that name is already used. This is unsafe in production
      --repo string              Chart repository url where to locate the requested chart
      --set stringArray          Set values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
      --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)
      --set-string stringArray   Set STRING values on the command line (can specify multiple or separate values with commas: key1=val1,key2=val2)
      --timeout int              Time in seconds to wait for any individual Kubernetes operation (like Jobs for hooks) (default 300)
      --tls                      Enable TLS for request
      --tls-ca-cert string       Path to TLS CA certificate file (default "$HELM-HOME/ca.pem")
      --tls-cert string          Path to TLS certificate file (default "$HELM-HOME/cert.pem")
      --tls-hostname string      The server name used to verify the hostname on the returned certificates from the server
      --tls-key string           Path to TLS key file (default "$HELM-HOME/key.pem")
      --tls-verify               Enable TLS for request and verify remote
      --username string          Chart repository username where to locate the requested chart
  -f, --values valueFiles        Specify values in a YAML file or a URL(can specify multiple) (default [])
      --verify                   Verify the package before installing it
      --version string           Specify the exact chart version to install. If this is not specified, the latest version is installed
      --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

Options inherited from parent commands

      --debug                           Enable verbose output
      --home string                     Location of your Helm config. Overrides $HELM-HOME (default "~/.helm")
      --host string                     Address of Tiller. Overrides $HELM-HOST
      --kube-context string             Name of the kubeconfig context to use
      --kubeconfig string               Absolute path of the kubeconfig file to be used
      --tiller-connection-timeout int   The duration (in seconds) Helm will wait to establish a connection to Tiller (default 300)
      --tiller-namespace string         Namespace of Tiller (default "kube-system")

SEE ALSO

• helm - The Helm package manager for Kubernetes.

Auto generated by spf13/cobra on 24-Sep-2019