jonathan-ostrander opened a new issue, #39693:
URL: https://github.com/apache/airflow/issues/39693
### Apache Airflow version
main (development)
### If "Other Airflow 2 version" selected, which one?
_No response_
### What happened?
A `KubernetesPodOperator` with the following `full_pod_spec`:
```yaml
apiVersion: v1
kind: Pod
metadata:
name: multi-container-pod
spec:
restartPolicy: Never
containers:
- name: base
image: busybox
command: ["sh", "-c", "echo base will exit after 30 seconds; sleep 30"]
- name: sidecar
image: busybox
command: ["sh", "-c", "echo sidecar running indefinitely; while true; do
sleep 3600; done"]
```
will not mark the task as successful after 30 seconds because the `sidecar`
will continue to run after the `base` container has succeeded. This happens
because the `pod_manager` gets stuck waiting for pod completion. [This if
statement returns `False` when istio is not enabled on the
pod.](https://github.com/apache/airflow/blob/8b19b78ba50835423a5385a64c31a0e950548147/airflow/providers/cncf/kubernetes/utils/pod_manager.py#L621-L622)
### What you think should happen instead?
The pod should be considered complete when the base container succeeds
regardless of whether or not any other containers on the pod are still running.
### How to reproduce
Create a `KubernetesPodOperator` with the `full_pod_spec` provided.
### Operating System
MacOS 14.4.1
### Versions of Apache Airflow Providers
`apache-airflow-providers-cncf-kubernetes==8.0.1`
### Deployment
Other
### Deployment details
Kubernetes on Google Kubernetes Engine. Kubernetes executors and worker pods
all run on the same cluster.
### Anything else?
_No response_
### Are you willing to submit PR?
- [X] 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]
