tokoko opened a new issue, #34495: URL: https://github.com/apache/airflow/issues/34495
### Description Right now only optional components (triggerer, dag-processor) can be disabled from values.yaml in helm chart. I'd like to have the same functionality for core components as well (webserver, scheduler and workers even if Celery is configured). ### Use case/motivation I am trying to setup Airflow deployment for multiple teams. The way I hope to achieve it is too have multiple helm releases for the overall environment instead of just one. - the core helm release will contain only the core components that are shared - webserver, scheduler, triggerrer. - Additional per-team helm releases will reuse some of the configuration (database connections, etc) but only deploy team-specific components (dag-processor and workers that will be configured to consume dags only from this team's dag-processor). This way teams will have flexibility to configure their Python environments freely and also have an isolated release cycle. The primary blocker for achieving this setup with official helm chart is the fact that most of the components can't be easily disabled from values.yaml ### Related issues _No response_ ### Are you willing to submit a PR? - [X] 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]
