dagProcessor is missing podDisruptionBudget

[geocomm-shenningsgard]

Official Helm Chart version

1.18.0 (latest released)

Apache Airflow version

3.x

Kubernetes Version

1.32

Helm Chart configuration

dagProcessor:
#  podDisruptionBudget:
#    enabled: true
#    config:
#      maxUnavailable: 1
scheduler:
  podDisruptionBudget:
    enabled: true
    config:
      maxUnavailable: 1
apiServer:
  podDisruptionBudget:
    enabled: true
    config:
      maxUnavailable: 1
web:
  podDisruptionBudget:
    enabled: true
    config:
      maxUnavailable: 1

Docker Image customizations

No response

What happened

The dagProcessor config doesn't allow any podDisruptionBudget.

What you think should happen instead

It should allow configuration of a podDisruptionBudget, as all of the other components do.

How to reproduce

Add this to a values.yaml file:

dagProcessor:
  podDisruptionBudget:
    enabled: true
    config:
      maxUnavailable: 1

...then try to deploy Airflow via the Helm chart.

Anything else

No response

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

[Arunodoy18]

Thanks for raising this.unlike other core components, dagProcessor currently does not create a PodDisruptionBudget even when configured in values.yaml.I’ll work on adding PDB support for dagProcessor,Hope this works.Cheers