CODEWITHSUNDEEP
kubernetes-helm
RAMNEEK GUPTA
RAMNEEK GUPTA

Reputation: 783

ingress.yaml template returns error in renderring --> nil pointer evaluating interface {}.service

I am installing a helm chart which has a ingress.yaml template.

I get this error:

Error: render error in "chartmuseum/templates/ingress.yaml": template: chartmuseum/templates/ingress.yaml:35:22: executing "chartmuseum/templates/ingress.yaml" at <.Values.service.servicename>: nil pointer evaluating interface {}.service

I am not able to find where the problem is. The same set of if else structure works abolutely fine in the service.yaml of the same helm chart.

- path: {{ default "/" .path | quote }}
        backend:
        {{- if .Values.service.servicename }}
          serviceName: {{ .Values.service.servicename }}
        {{- else }}
          serviceName: {{ include "chartmuseum.fullname" . }}
        {{- end }}

Getting error on this line --> serviceName: {{ .Values.service.servicename }}

The code that works in service.yaml fine is

metadata:
{{- if .Values.service.servicename }}
  name: {{ .Values.service.servicename }}
{{- else }}
  name: {{ include "chartmuseum.fullname" . }}
{{- end }}

Expected result: if there is a servcice.servicename in values in values.yaml file , the ingress should pick the value from there for the key serviceName. Else it should include "chartmuseum.fullname".

The same structure works fine for service.yaml.

Below is the url of the original helm chart that i am using.

https://github.com/helm/charts/tree/master/stable/chartmuseum

I just modified the ingress.yaml to add if else block around line 31. Ingress.yaml https://github.com/helm/charts/blob/master/stable/chartmuseum/templates/ingress.yaml

Values.yaml file is insignificant. I have the below values in it

service:
  servicename: helm-charts-test

but even without this value, the if else block is expected to work.

Upvotes: 42

Views: 82037

Answers (3)

Narasimha Pasupuleti
Narasimha Pasupuleti

Reputation: 11

I have faced same issue. Try checking by linking values.yaml. If it returns no errors, then there is no issue with indentations. Then check if the values.yaml file name; if v is V or v is small v. It worked for me after changing the name of file from Values.yaml to values.yaml.

helm lint -f C:\\Users\\pasup\\Documents\\narasimhachart\\values.yaml C:\\Users\\pasup\\Documents\\narasimhachart

Upvotes: 0

krzk
krzk

Reputation: 431

I followed this answer by @Torrey and replaced

targetPort: {{ .Values.non_existing.port | default 1234 }}

with

targetPort: {{ (.Values.non_existing).port | default 1234 }}

and it worked

Upvotes: 16

Yaniv Oliver
Yaniv Oliver

Reputation: 3971

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 order to access the Values as expected.

For your scenario, it would be something like:

- path: {{ default "/" .path | quote }}
        backend:
        {{- if $.Values.service.servicename }}
          serviceName: {{ $.Values.service.servicename }}
        {{- else }}
          serviceName: {{ include "chartmuseum.fullname" $ }}
        {{- end }}

See here for more details.

Upvotes: 86

Related Questions