Skip to content

Conversation

@jscheffl
Copy link
Contributor

Had an excessive day checking for problems today and realized that K8sPodOperator produces a bit too much log noise in my view. I think it is okay to inform if no XCom is found but printing the XCom to logs is actually not needed as it is published as XCom anyway.

Therefore I propose to remove this... actually propose to keep it for debugging purposes but propose to keep logs clean in usual operations.

I am not sure if there is any legacy reason behind this. let me know if this is an important "feature". Then I can add (oh not yet another) config flag.

@boring-cyborg boring-cyborg bot added area:providers provider:cncf-kubernetes Kubernetes (k8s) provider related issues labels Jun 16, 2025
@jedcunningham
Copy link
Member

You could argue we shouldn't print them ever - they (xcom and task logs) are separate permissions after all.

@jscheffl jscheffl merged commit 35bc037 into apache:main Jun 18, 2025
80 checks passed
RoyLee1224 pushed a commit to RoyLee1224/airflow that referenced this pull request Jun 21, 2025
@jscheffl jscheffl deleted the bugfix/reduce-log-noise-from-k8s-operator branch October 5, 2025 07:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:cncf-kubernetes Kubernetes (k8s) provider related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants