kosteev opened a new issue, #56360: URL: https://github.com/apache/airflow/issues/56360
### Apache Airflow version 3.1.0 ### If "Other Airflow 2 version" selected, which one? _No response_ ### What happened? Using KubernetesPodOperator in Airflow 3 generates some not-useful warning/errors. <img width="1866" height="534" alt="Image" src="https://github.com/user-attachments/assets/45aec7e4-cb09-44b9-9324-7b1f0ccf2e54"; /> While running KubernetesPodOperator and using default kubernetes connection id "kubernetes_default", the Kubernetes hook will fallback to cluster-derived credentials: https://github.com/apache/airflow/blob/767ae70fbc12b80363c58bc8dfba020c5bfb26e2/providers/cncf/kubernetes/src/airflow/providers/cncf/kubernetes/hooks/kubernetes.py#L183 This works as expected, but generates warning/error message - see screenshot above. ### What you think should happen instead? _No response_ ### How to reproduce 1. Run Airflow 3 instance 2. Deploy DAG ``` import datetime from airflow import models from airflow.providers.cncf.kubernetes.operators.pod import KubernetesPodOperator with models.DAG( dag_id="kpo_simple_echo", schedule=None, start_date=datetime.datetime(2000, 1, 1), ) as dag: KubernetesPodOperator( task_id="kpo_simple_echo", name="kpo-simple-echo", cmds=["bash"], arguments=["-c", "echo ZZZZZZZ"], image="gcr.io/gcp-runtimes/ubuntu_20_0_4", config_file="{path to kube config}", ) ``` 3. Observe logs ### Operating System linux ### Versions of Apache Airflow Providers _No response_ ### Deployment Google Cloud Composer ### Deployment details _No response_ ### 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]
