Values Files

In the previous section we looked at the built-in objects that Helm templates offer. One of the built-in objects is Values. This object provides access to values passed into the chart. Its contents come from multiple sources:

  • The values.yaml file in the chart
  • If this is a subchart, the values.yaml file of a parent chart
  • A values file if passed into helm install or helm upgrade with the -f flag (helm install -f myvals.yaml ./mychart)
  • Individual parameters passed with --set (such as helm install --set foo=bar ./mychart)

The list above is in order of specificity: values.yaml is the default, which can be overridden by a parent chart’s values.yaml, which can in turn be overridden by a user-supplied values file, which can in turn be overridden by --set parameters.

Values files are plain YAML files. Let’s edit mychart/values.yaml and then edit our ConfigMap template.

Removing the defaults in values.yaml, we’ll set just one parameter:

  1. favoriteDrink: coffee

Now we can use this inside of a template:

  1. apiVersion: v1
  2. kind: ConfigMap
  3. metadata:
  4.   name: {{ .Release.Name }}-configmap
  5. data:
  6.   myvalue: "Hello World"
  7.   drink: {{ .Values.favoriteDrink }}

Notice on the last line we access favoriteDrink as an attribute of Values: {{ .Values.favoriteDrink }}.

Let’s see how this renders.

  1. $ helm install geared-marsupi ./mychart --dry-run --debug
  2. install.go:158: [debug] Original chart version: ""
  3. install.go:175: [debug] CHART PATH: /home/bagratte/src/playground/mychart
  5. NAME: geared-marsupi
  6. LAST DEPLOYED: Wed Feb 19 23:21:13 2020
  7. NAMESPACE: default
  8. STATUS: pending-install
  9. REVISION: 1
  10. TEST SUITE: None
  11. USER-SUPPLIED VALUES:
  12. {}
  14. COMPUTED VALUES:
  15. favoriteDrink: coffee
  17. HOOKS:
  18. MANIFEST:
  19. ---
  20. # Source: mychart/templates/configmap.yaml
  21. apiVersion: v1
  22. kind: ConfigMap
  23. metadata:
  24.   name: geared-marsupi-configmap
  25. data:
  26.   myvalue: "Hello World"
  27.   drink: coffee

Because favoriteDrink is set in the default values.yaml file to coffee, that’s the value displayed in the template. We can easily override that by adding a --set flag in our call to helm install:

  1. $ helm install solid-vulture ./mychart --dry-run --debug --set favoriteDrink=slurm
  2. install.go:158: [debug] Original chart version: ""
  3. install.go:175: [debug] CHART PATH: /home/bagratte/src/playground/mychart
  5. NAME: solid-vulture
  6. LAST DEPLOYED: Wed Feb 19 23:25:54 2020
  7. NAMESPACE: default
  8. STATUS: pending-install
  9. REVISION: 1
  10. TEST SUITE: None
  11. USER-SUPPLIED VALUES:
  12. favoriteDrink: slurm
  14. COMPUTED VALUES:
  15. favoriteDrink: slurm
  17. HOOKS:
  18. MANIFEST:
  19. ---
  20. # Source: mychart/templates/configmap.yaml
  21. apiVersion: v1
  22. kind: ConfigMap
  23. metadata:
  24.   name: solid-vulture-configmap
  25. data:
  26.   myvalue: "Hello World"
  27.   drink: slurm

Since --set has a higher precedence than the default values.yaml file, our template generates drink: slurm.

Values files can contain more structured content, too. For example, we could create a favorite section in our values.yaml file, and then add several keys there:

  1. favorite:
  2.   drink: coffee
  3.   food: pizza

Now we would have to modify the template slightly:

  1. apiVersion: v1
  2. kind: ConfigMap
  3. metadata:
  4.   name: {{ .Release.Name }}-configmap
  5. data:
  6.   myvalue: "Hello World"
  7.   drink: {{ .Values.favorite.drink }}
  8.   food: {{ .Values.favorite.food }}

While structuring data this way is possible, the recommendation is that you keep your values trees shallow, favoring flatness. When we look at assigning values to subcharts, we’ll see how values are named using a tree structure.

Deleting a default key

If you need to delete a key from the default values, you may override the value of the key to be null, in which case Helm will remove the key from the overridden values merge.

For example, the stable Drupal chart allows configuring the liveness probe, in case you configure a custom image. Here are the default values:

  1. livenessProbe:
  2.   httpGet:
  3.     path: /user/login
  4.     port: http
  5.   initialDelaySeconds: 120

If you try to override the livenessProbe handler to exec instead of httpGet using --set livenessProbe.exec.command=[cat,docroot/CHANGELOG.txt], Helm will coalesce the default and overridden keys together, resulting in the following YAML:

  1. livenessProbe:
  2.   httpGet:
  3.     path: /user/login
  4.     port: http
  5.   exec:
  6.     command:
  7.     - cat
  8.     - docroot/CHANGELOG.txt
  9.   initialDelaySeconds: 120

However, Kubernetes would then fail because you can not declare more than one livenessProbe handler. To overcome this, you may instruct Helm to delete the livenessProbe.httpGet by setting it to null:

  1. helm install stable/drupal --set image=my-registry/drupal:0.1.0 --set livenessProbe.exec.command=[cat,docroot/CHANGELOG.txt] --set livenessProbe.httpGet=null

At this point, we’ve seen several built-in objects, and used them to inject information into a template. Now we will take a look at another aspect of the template engine: functions and pipelines.