o-nikolas opened a new issue, #27933: URL: https://github.com/apache/airflow/issues/27933
### Overview There are pages in the Airflow UI which are specific to particular Executors. ### Examples - **6a**) Kube yaml can be rendered in the UI for KubernetesExecutor and CeleryKubernetesExecutor, at the `/rendered-k8s` url. Views code: https://github.com/apache/airflow/blob/27e2101f6ee5567b2843cbccf1dca0b0e7c96186/airflow/www/views.py#L1480 Associated TI code: https://github.com/apache/airflow/blob/26f94c5370587f73ebd935cecf208c6a36bdf9b6/airflow/models/taskinstance.py#L2161 - **6b**) A warning popup is show in the UI when using the SequentialExecutor. Views code: https://github.com/apache/airflow/blob/26f94c5370587f73ebd935cecf208c6a36bdf9b6/airflow/www/views.py#L532 Associated message in dags.html: https://github.com/apache/airflow/blob/fb741fd87254e235f99d7d67e558dafad601f253/airflow/www/templates/airflow/dags.html#L115-L120 ### Proposal A pluggable mechanism for Executor subclasses to vend UI views to then be used in views.py. This would allow all Executors to have UI components without needing to modify core Airflow code. There are not many instance of this coupling and it would be a more involved implementation which might not be used often. It isn't as high priority as other coupling types, but should still be addressed. There are also projects underway to migrate Airflow UI to a different framework, which would likely affect how this coupling would be solved. -- 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]
