Helm install: Difference between revisions
Line 29: | Line 29: | ||
The -f|--values flag can be specified multiple time on the command line, and the rightmost value will take precedence. | 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 [Kubernetes_Cluster_Configuration_Concepts#ConfigMap|ConfigMap]] and can be viewed for a given release with helm get value <''release-name''>. <font color=darkgray>TODO: https://helm.sh/docs/using_helm/#the-format-and-limitations-of-set</font> | 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 [Kubernetes_Cluster_Configuration_Concepts#ConfigMap|ConfigMap]] and can be viewed for a given release with helm get value <''release-name''>. | ||
<font color=darkgray>TODO: https://helm.sh/docs/using_helm/#the-format-and-limitations-of-set</font> |
Revision as of 16:55, 28 August 2019
External
- https://helm.sh/docs/helm/#helm-install
- https://helm.sh/docs/using_helm/#helm-install-installing-a-package
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 [Kubernetes_Cluster_Configuration_Concepts#ConfigMap|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