The Helm template syntax is based on the Go programming language’s text/template package. The braces {{ and }} are the opening and closing brackets to enter and exit template logic. The Helm documentation at https://helm.sh/docs/chart_template_guide/control_structures/ discusses why this syntax is needed in an example. YAML ascribes meaning to whitespace, so managing the whitespace becomes pretty … Read more
The helm docu has a section The Format and Limitations of –set, which contains what you are looking for. –set outer.inner=value results in: outer: inner: value Therefore your whole helm command looks like this: helm install –set annotations.foo=bar,annotations.bash=baz stable/prometheus-redis-exporter
nameOverride replaces the name of the chart in the Chart.yaml file, when this is used to construct Kubernetes object names. fullnameOverride completely replaces the generated name. These come from the template provided by Helm for new charts. A typical object in the templates is named name: {{ include “<CHARTNAME>.fullname” . }} If you install a … Read more
Define the required values on top of your manifest as variables utilizing the required function. E.g. deployment.yaml: {{- $name := .Values.name | required “.Values.name is required.” -}} — apiVersion: apps/v1 kind: Deployment metadata: name: {{ $name }} ….
You need to enclose the key with quotations and then escape the dots helm install –values helm/jenkins.yml stable/jenkins –set Master.Ingress.Annotations.”certmanager\.k8s\.io/cluster-issuer”=letsencrypt-staging
From helm docs: icon: A URL to an SVG or PNG image to be used as an icon (optional). I.e.: apiVersion: v1 description: A Helm chart name: myChart version: 0.1.0 icon: https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_272x92dp.png
Might be worth trying using index method: xyz.abc-def: {{ index .Values.xyz “abc-def” }} looks like it’s still restricted by helm to allow hyphens in variable names (as well in subchart names) and index is a workaround
I ran into a similar problem and apparently it turns out Kubernetes’s Pod specification requires environment variable values to be coerced as strings, so integers need to be passed through quote.So, in your deployment.yaml file wherever you are using the numeric values try to pass them as below. value: {{ .Values.environment.TEMP | quote}} It will … Read more
Update 2: Helm 3 added support for multi namespaces https://github.com/helm/helm/issues/2060 Update 1: If a resource template specifies a metadata.namespace, then it will be installed in that namespace. For example, if I have a pod with metadata.namespace: x and I run helm install mychart –namespace y, that pod will be installed in x. I guess you … Read more
What you’re seeing is a weird caveat in Go templating. Your conditional logic is being evaluated inside a range loop. This means . you’re using to access Values is not the one you expect it to be, as it’s overridden for each range iteration evaluation. You can use $, which references the global scope in … Read more