templates/deployment.yaml contains the following block at line 697:
---
{{- if .Values.kafka.authentication.tls.enabled }}
...
{{- end }}
{{- if .Values.extraCoreComponentPodConfig }}
{{ toYaml .Values.extraCoreComponentPodConfig | indent 6 -}}
{{- end }}
which leads to the generation of a single extraCoreComponentPodConfig-block after rendering the template whenever it is defined. I'm quite sure the extraCoreComponentPodConfig-block should be inside the kafka.authentication.tls.enabled-block above.
For example if my values-file contains this:
extraCoreComponentPodConfig:
tolerations:
- key: faas
operator: Exists
effect: NoSchedule
the rendered template will contain this:
---
# Source: fission-all/templates/deployment.yaml
tolerations:
- effect: NoSchedule
key: faas
operator: Exists
---
which obviously isn't a valid kubernetes-object.
Tested in fission-all-1.12.0
templates/deployment.yamlcontains the following block at line 697:which leads to the generation of a single
extraCoreComponentPodConfig-block after rendering the template whenever it is defined. I'm quite sure theextraCoreComponentPodConfig-block should be inside thekafka.authentication.tls.enabled-block above.For example if my values-file contains this:
the rendered template will contain this:
which obviously isn't a valid kubernetes-object.
Tested in
fission-all-1.12.0