Gopal Dirisala

I am able to achieve the same using dynamic client. isn't it good idea to add it in the core_v1 apis?

> Nice findings. Looks promising. Thanks for that. > > Ok here's another scenario. > > The task OOMs and therefore cannot report its state by itself. I believe in...

@paramjeet01 You can mention airflow num_runs configuration parameter to restart the scheduler container based on your needs. https://airflow.apache.org/docs/apache-airflow/stable/configurations-ref.html

This issue is related to watcher is not able to scale and process the events on time. This leads to so many completed pods over the time. related: https://github.com/apache/airflow/issues/22612

We do have two metrics for the same. Can you check? ``` kubernetes_executor.clear_not_launched_queued_tasks.duration kubernetes_executor.adopt_task_instances.duration ``` https://airflow.apache.org/docs/apache-airflow/stable/administration-and-deployment/logging-monitoring/metrics.html

Build Prod Images still picking the google ads provider. ``` #56 25.60 ERROR: Ignored the following versions that require a different python version: 2.7.3 Requires-Python

@paramjeet01 Kubernetes executor and pod operator has gone multiple improvements in the past. I would request you try the latest versions and re-confirm the issue.

This issue is related to watcher is not able to scale and process the events on time. This leads to so many completed pods over the time. related: https://github.com/apache/airflow/issues/22612

@paramjeet01 Its a bug in the Kubernetes executor. I am going to work on the fix for the same.

> @dirrao in terms of numbers, how much improvement does this bring to the table? Just curious. > > Btw, wondering if there's any risk associated here with this. I...