[
https://issues.apache.org/jira/browse/AIRFLOW-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061995#comment-17061995
]
ASF subversion and git services commented on AIRFLOW-5448:
----------------------------------------------------------
Commit 86854482615425a3850e89f7e826512aed5cd367 in airflow's branch
refs/heads/v1-10-test from sjmiller609
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=8685448 ]
[AIRFLOW-5448] Handle istio-proxy for Kubernetes Pods (#62)
Istio service mesh is not compatible by default with Kubernetes Jobs.
The normal behavior is that a Job will be started, get an istio-proxy
sidecar attached to it via the istio mutating webhook, run until
completion, then the 'main' container in the pod stops, but istio-proxy
hangs around indefinitely. This change handles cleanly exiting the
Istio sidecar 'istio-proxy' when a Kubernetes Executor task completes.
(cherry picked from commit 84fa48f53a66a8ccf2b7b2910be49a69b697a6c5)
> Make Kubernetes Executor compatible with Istio service mesh
> -----------------------------------------------------------
>
> Key: AIRFLOW-5448
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5448
> Project: Apache Airflow
> Issue Type: Improvement
> Components: executor-kubernetes
> Affects Versions: 1.10.6
> Reporter: Steven Miller
> Assignee: Steven Miller
> Priority: Minor
>
> Istio service mesh is not compatible by default with Kubernetes Jobs. The
> normal behavior is that a Job will be started, get an istio-proxy sidecar
> attached to it via the istio mutating webhook, run until completion, then the
> 'main' container in the pod stops, but istio-proxy hangs around indefinitely.
> This applies to the Kubernetes Executor.
> Very recently, Istio implemented an endpoint that can be called to cleanly
> exit the proxy, specifically designed for this use case.
> - explanation: [https://github.com/istio/istio/issues/15041]
> - istio PR implementing it: [https://github.com/istio/istio/pull/15406]
> Astronomer will make a contribution to handle cleanly exit the istio-proxy by
> default. This will help Astronomer and other Airflow users making use of the
> Kubernetes Executor in combination with Istio.
> Original PR for solving this issue:
> [https://github.com/astronomer/airflow/pull/47]
> We will integrate into the Astronomer fork, then upstream after complying
> with all Airflow PR standards.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
