Open Roguito opened 1 month ago
this turned out to be related to the templating, and specifically: charts/argo-cd-6.0.6/argo-cd/templates/argocd-server/openshift/route.yaml and it's,
{{- if .Values.server.route.enabled -}} apiVersion: route.openshift.io/v1 kind: Route metadata: name: {{ template "argo-cd.server.fullname" . }} namespace: {{ .Release.Namespace | quote }} labels: {{- include "argo-cd.labels" (dict "context" . "component" .Values.server.name "name" .Values.server.name) | nindent 4 }} {{- with .Values.server.route.annotations }} annotations: {{- range $key, $value := . }} {{ $key }}: {{ $value | quote }} {{- end }} {{- end }} spec: host: {{ .Values.server.route.hostname | quote }} to: kind: Service name: {{ template "argo-cd.server.fullname" . }} weight: 100 port: targetPort: https tls: termination: {{ .Values.server.route.termination_type | quote }} insecureEdgeTerminationPolicy: {{ .Values.server.route.termination_policy | quote }} wildcardPolicy: None {{- end }}
evaluating to false. This would be the case if there were no server.route.enabled defined in the argocd helm chart's values file.
I don't use openshift and have moved on to the API gateway so I just removed the {{- if .Values.server.route.enabled -}} templating.
apologies... that did not actually fix it. Oh well,back to the drawing board.
Describe the bug
error: Error: template: argo-cd/templates/argocd-server/openshift/route.yaml:1:14: executing "argo-cd/templates/argocd-server/openshift/route.yaml" at <.Values.server.route.enabled>: nil pointer evaluating interface {}.route
Related helm chart
argo-cd
Helm chart version
6.0.6
To Reproduce
Expected behavior
Proper templating of this .Values.server.route.enabled
omitting it in value.yaml also produces the above errors. Explicitly providing is also does.
Screenshots
No response
Additional context
No response