[I] safe-to-evict annotation is not set when using KubernetesExecutor [airflow]

["csp33 (via GitHub)" <gi...@apache.org>]

csp33 opened a new issue, #37351:
URL: https://github.com/apache/airflow/issues/37351

   ### Official Helm Chart version
   
   1.11.0 (latest released)
   
   ### Apache Airflow version
   
   2.8.0
   
   ### Kubernetes Version
   
   1.29
   
   ### Helm Chart configuration
   
   ```yaml
   workers:
     safeToEvict: false
   ```
   
   ### Docker Image customizations
   
   _No response_
   
   ### What happened
   
   When running Airflow with `KubernetesExecutor`, the `workers.safeToEvict` configuration is not being used, as this field is only read in the workers deployment (used by `CeleryExecutor`).
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   1. Deploy Airflow using Kubernetes Executor. Set `workers.safeToEvict: false` in the chart
   2. Run a DAG
   3. Check worker pods annotations and see that the safe-to-evict one is missing
   
   ### Anything else
   
   Related PR: https://github.com/apache/airflow/pull/35130
   
   
   ### Are you willing to submit 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: commits-unsubscribe@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] safe-to-evict annotation is not set when using KubernetesExecutor [airflow]

["eladkal (via GitHub)" <gi...@apache.org>]

eladkal closed issue #37351: safe-to-evict annotation is not set when using KubernetesExecutor
URL: https://github.com/apache/airflow/issues/37351


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org