revisionHistoryLimit: 0 is silently ignored due to truthy check in templates

[cuerty]

Official Helm Chart version

1.18.0 (latest released)

Apache Airflow version

3.0.2

Kubernetes Version

v1.32.10

Helm Chart configuration

revisionHistoryLimit: 0

Docker Image customizations

No response

What happened

Setting revisionHistoryLimit: 0 in values.yaml is silently ignored. The rendered manifests do not include the revisionHistoryLimit field, causing Kubernetes to use its default value (10) instead of keeping zero old ReplicaSets.

What you think should happen instead

Setting revisionHistoryLimit: 0 should render revisionHistoryLimit: 0 in the deployment manifests, allowing users to disable ReplicaSet history retention.

How to reproduce

1. Set in values.yaml:

revisionHistoryLimit: 0

2. Render the templates:

helm template airflow apache-airflow/airflow --set revisionHistoryLimit=0 | grep -A2 revisionHistoryLimit

Anything else

The templates use a truthy check:

{{- if .Values.revisionHistoryLimit }}
revisionHistoryLimit: {{ .Values.revisionHistoryLimit }}
{{- end }}

In Go templates, 0 evaluates to false, so the block is skipped.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.