Helm uses the sprig library to provide lots of data manipulation functions, have a look at their docs for strings. You can use the {{ split }} function to do what you want. $parts := split “.” .Values.deployment.domain $parts._0
Dash removes the spaces from the output on the side it appears in the template: https://golang.org/pkg/text/template/#hdr-Text_and_spaces {{- if …}} The above will remove all spaces that appear before the if statement, so if the result of if prints something, it’ll be right after the last piece of text without any spaces.
I’ve bumped into the same issue when installing rancher on K3s, setting KUBECONFIG helped. export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
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 }} ….
Maybe would be helpful for someone experiencing similar issues. As for me, a forgot to specify hostname in Ingress yaml file for both rules and tls sections. After duplicating the hostname, it started responding with a proper certificate. Example: apiVersion: networking.k8s.io/v1beta1 kind: Ingress metadata: name: test-web-ingress annotations: kubernetes.io/ingress.class: nginx spec: tls: – hosts: – my.host.com … Read more
The generated value .Release.Namespace is case-sensitive. The letter N in “namespace” should be capitalized.
This is or has been a helm issue for a while. It only affects the situation where the first install of a chart fails and has up to helm 2.7 required a manual delete of the failed release before correcting the issue and installing again. However there is now a –force flag available to address … Read more
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
According to https://github.com/kubernetes/helm/issues/1987#issuecomment-280497496, you set multiple values using curly braces, for example: –set foo={a,b,c} So, in your case it would be like this –set aws.subnets={subnet-123456,subnet-654321}