[BUG] Helm chart 2.20.0 in registry contains broken manager deployment template for global tolerations

[Sokratis1904]

The Helm chart published as kedacore/keda version 2.20.0 contains a broken templates/manager/deployment.yaml template in the packaged chart artifact. When .Values.tolerations is set and .Values.operator.tolerations is not set, helm template / helm upgrade renders invalid YAML and fails with:

YAML parse error on keda/templates/manager/deployment.yaml: error converting YAML to JSON: yaml: line 134: mapping values are not allowed in this context

The issue is not caused by invalid user values. The root cause is that the packaged chart in the Helm registry contains a faulty tolerations branch:

{{- if .Values.operator.tolerations }}
tolerations:
  {{- toYaml .Values.operator.tolerations | nindent 8 }}
{{- else if .Values.tolerations }}
  {{- toYaml .Values.tolerations }}
{{- end }}

In the else if .Values.tolerations branch, the tolerations: key is missing, which causes invalid YAML to be emitted under spec.template.spec.

The current template in the GitHub repository appears to be corrected, but the published Helm chart package for 2.20.0 is still broken.

Expected Behavior

Setting global tolerations in values.yaml should render valid Kubernetes YAML for the operator deployment, for example:

tolerations:
  - key: supernode
    operator: Equal
    value: "true"
    effect: NoSchedule

helm template and helm upgrade should succeed when only .Values.tolerations is provided.

Actual Behavior

When only .Values.tolerations is set, rendering the published Helm chart kedacore/keda version 2.20.0 fails with:

Error: YAML parse error on keda/templates/manager/deployment.yaml: error converting YAML to JSON: yaml: line 134: mapping values are not allowed in this context

The failure occurs because the packaged chart renders the list from .Values.tolerations without the required tolerations: key.

Steps to Reproduce the Problem

1. Create a values.yaml with global tolerations only:

 tolerations:
- key: infrastructure
  operator: Equal
  value: "true"
  effect: NoSchedule

2. Render the published chart from the Helm registry:

 helm template keda kedacore/keda \
--namespace keda \
--version 2.20.0 \
-f values.yaml \
--show-only templates/manager/deployment.yaml \
--debug

3. Observe the rendering failure:

Error: YAML parse error on keda/templates/manager/deployment.yaml: error converting YAML to JSON: yaml: line 134: mapping values are not allowed in this context

4. Compare the packaged chart template with the current GitHub version and observe that the GitHub version contains corrected logic, while the Helm registry package still contains the faulty template.

Specifications

• KEDA Version: 2.20.0 Helm chart
• Platform & Version: Helm CLI, chart pulled from kedacore/keda Helm registry
• Kubernetes Version: Not cluster-specific; reproducible during local chart rendering with helm template
• Scaler(s): Not applicable

Optional note for maintainers:
The problematic section in the published chart is:

{{- if .Values.operator.tolerations }}
tolerations:
  {{- toYaml .Values.operator.tolerations | nindent 8 }}
{{- else if .Values.tolerations }}
  {{- toYaml .Values.tolerations }}
{{- end }}

The updated deployment.yaml in repo works and should be packed into helm package asap!

[wozniakjan]

too late, there were already four before you :)

• Use of .Values.tolerations broken in chart version 2.20.0 #861
• The v2.2.0 keda helmchart is broken when added tolerations #865
• [BUG] v2.20.0: global tolerations in values.yaml causes YAML parse error in manager/deployment.yaml #866
• Missing nindent in manager/deployment tolerations v2.20.0 #868

should be fixed in 2.20.1

[Sokratis1904]

@wozniakjan thank you for your reply and sorry, didnt see the other issues related to this topic.

Any timelime for 2.20.1? Flux-Deployment is currently broken and would check if I roll back to previous version or just wait a few hours for the fix.

Thank you!

[wozniakjan]

good news - https://github.com/kedacore/charts/releases/tag/v2.20.1