[bitnami/airflow] Allow multiple executors with CeleryExecutor #35423
+18
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
Allow use of multiple executors as available since Airflow 2.10.0
See related Container PR
This is a follow up to #29107
Benefits
Airflow 3.x does not allow hybrid executors to be used anymore in favor of the multiple executor syntax.
The current Bitnami chart for 3.0.3 will not spawn a celery worker when using the new multiple executor syntax because it is checking for an exact match on
CeleryExecutor
.Making effectively impossible to deploy a hybrid Celery/k8s environment with 3.0.3.
Possible drawbacks
The condition change preserves backwards compatibility so I don't see any.
Applicable issues
Additional information
The rest of the checklist will be done when the container PR is merged
Checklist
Chart.yaml
according to semver. This is not necessary when the changes only affect README.md files.README.md
using readme-generator-for-helm