Kubernetes PodManager's xcom sidecar kill command is invalid for containers where /bin/sh is dash

[pdebelak]

Apache Airflow version

2.8.2

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

No response

What happened?

When using a kubernetes connection that has an XCom sidecar image value set to an image where /bin/sh is dash, the pod manager attempts to run kill -s SIGINT 1 using /bin/sh which prints kill: invalid signal number or name: SIGINT and fails to kill the process. This works fine with the default alpine image, but not with debian-based ones (like the default python image). See

airflow/airflow/providers/cncf/kubernetes/utils/pod_manager.py

Line 776 in 2852976

def extract_xcom_kill(self, pod: V1Pod):

for the code for this.

What you think should happen instead?

The pod manager should either let you customize the shell used (so I can specify /bin/bash instead of /bin/sh) or should use the more portable signal numbers instead (kill -2 1, which is the equivalent command) which should work with any container with a POSIX /bin/sh.

How to reproduce

Set the XCom sidecar image for a kubernetes connection to python:latest and then use that connection to start a task with the KubernetesPodOperator with do_xcom_push=True. Notice that the sidecar prints an error and doesn't terminate.

Operating System

Debian GNU/Linux

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