orenl91 opened a new issue, #33184: URL: https://github.com/apache/airflow/issues/33184
### Apache Airflow version Other Airflow 2 version (please specify below) ### What happened Apache Airflow version 2.5.3 (on Google Composer) What happened Kubernetes pod operator failed to push xcom value. After upgrading airflow from 2.3.4 to 2.5.3 (and apache-airflow-providers-cncf-kubernetes from 5.2.0 to 7.2.0) pushing of xcom values from kubernetes pod operator stopped working. attaching the log and xcom screen   ### What you think should happen instead A new XCOM value should appear in XCOM screen ### How to reproduce Using Google Cloud Composer 2.3.5 with Airflow 2.5.3 ### Operating System Google Cloud Composer Managed Airflow ### Versions of Apache Airflow Providers From Google Documentation : https://cloud.google.com/composer/docs/concepts/versioning/composer-versions apache-airflow==2.5.3+composer apache-airflow-providers-apache-beam==5.1.1 apache-airflow-providers-cncf-kubernetes==7.2.0 apache-airflow-providers-common-sql==1.6.0 apache-airflow-providers-dbt-cloud==3.2.2 apache-airflow-providers-ftp==3.4.2 apache-airflow-providers-google==10.3.0 apache-airflow-providers-hashicorp==3.4.2 apache-airflow-providers-http==4.4.2 apache-airflow-providers-imap==3.2.2 apache-airflow-providers-mysql==5.1.1 apache-airflow-providers-postgres==5.5.2 apache-airflow-providers-sendgrid==3.2.1 apache-airflow-providers-sqlite==3.4.2 apache-airflow-providers-ssh==3.7.1 ### 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]
