pierrejeambrun opened a new issue, #42322: URL: https://github.com/apache/airflow/issues/42322
### Body Figure out how the architecture of the APIs will look like from a deployment (CLI, processes, Helm Chart) and source code perspective. Some of the constraints are: - Keep compatibility with FAB and legacy plugin system - Allow users to run the task sdk API as a standalone. - Think about the deployment complexity implied by additional reverse proxy or additional processes. This could consist of a spike exploring how this could work or putting that on paper via an architecture diagram as requested by @jscheffl in the last airflow 3 dev call. ### Committer - [X] I acknowledge that I am a maintainer/committer of the Apache Airflow project. -- 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]
