Helm Chart values.yaml: Difference between revisions
Line 17: | Line 17: | ||
All string values should be quoted, everything else should use implicit type conversion. Also see [[YAML#Data_Types|YAML Data Types]]. | All string values should be quoted, everything else should use implicit type conversion. Also see [[YAML#Data_Types|YAML Data Types]]. | ||
Values specified in this file can be potentially overridden by values specified with --set, so it is a good idea to come up with variable names that can be easily overridden this way. For example: | |||
servers: | |||
first: | |||
port: 80 | |||
if preferable to: | |||
servers: | |||
- name: first | |||
port: 80 | |||
because in the first case the override is: | |||
--set servers.first.port=81 | |||
while in the second case is: | |||
--set servers[0].port=81 | |||
which is sensitive to the potential change in order. | |||
=Example= | =Example= |
Revision as of 22:37, 28 August 2019
Internal
Overview
The default configuration values for a chart. The file is mandatory. The content of this file is displayed by helm inspect values.
Values Best Practices
Variable name should begin with a lowercase letter, and words should be separated with camelcase. All of Helm’s built-in variables begin with an uppercase letter to easily distinguish them from user-defined values.
All string values should be quoted, everything else should use implicit type conversion. Also see YAML Data Types.
Values specified in this file can be potentially overridden by values specified with --set, so it is a good idea to come up with variable names that can be easily overridden this way. For example:
servers: first: port: 80
if preferable to:
servers: - name: first port: 80
because in the first case the override is:
--set servers.first.port=81
while in the second case is:
--set servers[0].port=81
which is sensitive to the potential change in order.
Example
imageRegistry: "quai.io/something" dockerTag: "latest" pullPolicy: "always" storage: "s3"