You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Steven Miller (Jira)" <ji...@apache.org> on 2019/09/09 16:15:00 UTC
[jira] [Updated] (AIRFLOW-5448) Make Kubernetes Executor compatible
with Istio service mesh
[ https://issues.apache.org/jira/browse/AIRFLOW-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Miller updated AIRFLOW-5448:
-----------------------------------
Description:
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.
Here is the 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.
was:
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.
Here is the 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.
> 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.
> Here is the 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.2#803003)