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

   ### Apache Airflow Provider(s)
   
   cncf-kubernetes, google
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Apache Airflow version
   
   2.10.5
   
   ### Operating System
   
   Linux
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### Deployment details
   
   Using official Docker image in k8s (issue is related to usage of 
GKEStartPodOperator)
   
   ### What happened
   
   Somewhere 
https://github.com/apache/airflow/blob/2b1c2758f41e438280380a1e11b61d6b0085ee7c/providers/google/src/airflow/providers/google/cloud/operators/kubernetes_engine.py#L641
 a new approach to pod deletion is utilized so we are on par with CNCF k8s 
package enum OnFinishAction. Unfortunately the values set there don't compare 
with the values withing CNCF k8s package (maybe it's because differences in 
imports) resulting in failing equality tests here 
https://github.com/apache/airflow/blob/2b1c2758f41e438280380a1e11b61d6b0085ee7c/providers/cncf/kubernetes/src/airflow/providers/cncf/kubernetes/operators/pod.py#L1047
   
   ### What you think should happen instead
   
   I guess another way to compare the enums could be used here so the pods are 
deleted if operator is properly configured.
   
   ### How to reproduce
   
   Use GKEStartPodOperator to run a job in k8s environment with 
on_finish_action='DELETE_POD' - the pod will be kept with message "Skipping 
deleting pod" instead of deletion.
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to