crabio commented on issue #36998: URL: https://github.com/apache/airflow/issues/36998#issuecomment-2062032563
@aru-trackunit Sure 1. run Airflow with Kubernetes Executor with 1 scheduler 2. run some tasks in your default namespace (maybe it is not required) and run tasks in another namespace with access for Airflow for create, watch and delete pods 3. run airflow with active tasks for some time. Need to have running tasks for some time to catch slots leak. Maybe tasks in another namespace not required, because we faced this issue before we started using multiple namespaces. I think @paramjeet01 and @smhood has 1 namespace -- 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]
