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

   ### Apache Airflow version
   
   Other Airflow 2 version (please specify below)
   
   ### If "Other Airflow 2 version" selected, which one?
   
   2.7
   
   ### What happened?
   
   I upgraded from airflow version 2.5.3 to 2.7.1 and with that 
apache-airflow-providers-cncf-kubernetes was also upgraded from 5.2.2 to 7.5.0.
   
   Earlier I was using Kubernetes connection ID like this from Xcoms. I put it 
in xcoms in the first task where I load all the configs to xcoms
   `kubernetes_conn_id: "{% raw %}{{ ti.xcom_pull(key ='env_vars', 
task_ids='fetch_vars')['{% endraw %}{{root_key}}{% raw 
%}']['kubernetes_conn_id']}}{% endraw %}"`
   
   This was working fine, but after upgrading this stopped working and I am 
getting the following error
   `The conn_id `{{ ti.xcom_pull(key ='env_variables', 
task_ids='fetch_env')['cycle_process_client_2332']['kubernetes_conn_id']}}` 
isn't defined`
   
   Also in the UI if I check rendered templates tag I can see the conn ID 
resolved correctly. I am confused, any help is appreciated.
   
   ### What you think should happen instead?
   
   It should pull the connection ID correctly from the Xcoms.
   
   ### How to reproduce
   
   Create a dag with and add a task using SparkKubernetesOperator, pass 
kubernetes_conn_id as a param and assign it Xcom value.
   
   ### Operating System
   
   linux
   
   ### Versions of Apache Airflow Providers
   
    apache-airflow-providers-cncf-kubernetes - 7.5
   airflow - 2.7
   
   ### Deployment
   
   Other Docker-based deployment
   
   ### 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]

Reply via email to