The xcom sidecar container to be in the running state before we exec against it.

[Lechufane]

Apache Airflow version

main (development)

If "Other Airflow 2 version" selected, which one?

No response

What happened?

There is no guarantee that the xcom sidecar container will have been running by the time the extract_xcom is used by KPO's execute even if we wait for pod to be a "Running" state - this further means if the base container has completed before the xcom sidecar container is running, the entire operator fails because you cannot exec against a non-running container.

What you think should happen instead?

Before we exec against it, it needs to wait for the Xcom sidecar container to be in "running" state.

How to reproduce

Have a k8s cluster that can reproduce the behavior of the Xcom container not starting when the base container has been completed, and check that Xcom extraction was successful.

Operating System

Windows

Versions of Apache Airflow Providers

No response

Deployment

Official Apache Airflow Helm Chart

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

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.