Key benefits of Helm is that it helps reduce the amount of configuration a user needs to provide to deploy applications to Kubernetes. With Helm, we can have a single chart that can deploy all the microservices.
Unique ServiceAccount
Recently we wanted to create a unique service account for each microservice, so all microservices don’t share same service account using helm template. In our example, we will append the release name with the service account name.
Using join function
{{ (list .Values.serviceAccount.name (include "openjdk.fullname" .) | join "-") }}
Adding fail condition
{{- if .Values.serviceAccount.name -}}
{{ (list .Values.serviceAccount.name (include "openjdk.fullname" .) | join "-") }}
{{- else -}}
{{- fail "Please enter a name for service account to create." }}
{{- end -}}
Full example
{{- define "openjdk.serviceAccountName" -}}
{{- if .Values.serviceAccount.create -}}
{{- if .Values.serviceAccount.name -}}
{{ (list .Values.serviceAccount.name (include "openjdk.fullname" .) | join "-") }}
{{- else -}}
{{- fail "Please enter a name for service account to create." }}
{{- end -}}
{{- else -}}
{{- if .Values.serviceAccount.name -}}
{{ (list .Values.serviceAccount.name (include "openjdk.fullname" .) | join "-") }}
{{- else -}}
"default"
{{- end -}}
{{- end -}}
{{- end -}}
Another way to manipulate strings in helpers.tpl is using printf
{{- define "ocp-openjdk.hostname" -}}
{{- printf "%s-%s%s" .Release.Name .Release.Namespace (.Values.subdomain | default ".apps.amp01.nonprod" ) -}}
{{- end -}}