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

   ### Apache Airflow Provider(s)
   
   cncf-kubernetes
   
   ### Versions of Apache Airflow Providers
   
   In one of the latest cncf-kubernetes provider we emit warning message:
   """
   
/opt/python3.11/lib/python3.11/site-packages/airflow/providers/cncf/kubernetes/executors/kubernetes_executor.py:155
 AirflowProviderDeprecationWarning: Configuration 'namespace' is deprecated. 
Use 'pod_template_file' to specify the namespace instead. 
   """
   
https://github.com/apache/airflow/blob/875a427ab3f1cc06bf470a9cebdd27aa8d9528a5/providers/cncf/kubernetes/src/airflow/providers/cncf/kubernetes/kube_config.py#L85
   
   However it is still needed/used in kubernetex_executor_utils.py:
   
https://github.com/apache/airflow/blob/875a427ab3f1cc06bf470a9cebdd27aa8d9528a5/providers/cncf/kubernetes/src/airflow/providers/cncf/kubernetes/executors/kubernetes_executor_utils.py#L523C53-L523C67
   
   So, this property is actually needed and shouldn't be deprecated?
   
   ### Apache Airflow version
   
   3.1.0
   
   ### Operating System
   
   Linux
   
   ### Deployment
   
   Google Cloud Composer
   
   ### Deployment details
   
   _No response_
   
   ### What happened
   
   _No response_
   
   ### What you think should happen instead
   
   _No response_
   
   ### How to reproduce
   
   Use latest cncf-kubernetes provider and run Airflow with KubernetesExecutor
   
   ### 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