Helm install: Difference between revisions
Line 33: | Line 33: | ||
<font color=darkgray>TODO: https://helm.sh/docs/using_helm/#the-format-and-limitations-of-set</font> | <font color=darkgray>TODO: https://helm.sh/docs/using_helm/#the-format-and-limitations-of-set</font> | ||
===Overriding Tags and Conditions=== | |||
Use --set. | |||
==Installing from Different Sources== | ==Installing from Different Sources== |
Revision as of 21:27, 28 August 2019
External
- https://helm.sh/docs/helm/#helm-install
- https://helm.sh/docs/using_helm/#helm-install-installing-a-package
- https://helm.sh/docs/using_helm/#helpful-options-for-install-upgrade-rollback
Internal
Overview
Install a chart archive, creating a release in the process.
helm install <chart-name> helm install stable/mysql
Specifying a Release Name
helm install --name <release-name> ...
Overriding Default Configuration
Default configuration - or just some values - can be overridden in bulk with:
helm install -f|--values <configuration-overrides-file.yaml> <chart name>
The -f|--values flag can be specified multiple time on the command line, and the rightmost value will take precedence.
Individual configuration options can be specified with --set, --set-string and --set-file. If both --set and --values are used, the --set-specified configuration values are merged into the configuration values specified with --values, with higher precedence. Overrides specified with --set are persisted in a ConfigMap and can be viewed for a given release with helm get value <release-name>.
TODO: https://helm.sh/docs/using_helm/#the-format-and-limitations-of-set
Overriding Tags and Conditions
Use --set.
Installing from Different Sources
The default option for the helm install command is to install from the default repository. However, the chart may come from different sources:
Installing from a File
helm install something-0.1.1.tgz
Installing from an Unpacked Chart Directory
helm install ./something
Installing from a URL
helm install https://example.com/charts/something-1.0.0.tgz