geocomm-shenningsgard opened a new issue, #60242:
URL: https://github.com/apache/airflow/issues/60242
### Official Helm Chart version
1.18.0 (latest released)
### Apache Airflow version
3.x
### Kubernetes Version
1.32
### Helm Chart configuration
```yaml
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:
```yaml
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
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]