You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Pat Carroll (Jira)" <ji...@apache.org> on 2020/01/23 10:29:00 UTC
[jira] [Updated] (AIRFLOW-6618) kubernetes_pod_operator no longer
using kube context in provided config_file
[ https://issues.apache.org/jira/browse/AIRFLOW-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pat Carroll updated AIRFLOW-6618:
---------------------------------
Description:
Call KubernetesPodOperator and provide kubernetes context via a config_file.
e.g.
{{doPod = KubernetesPodOperator(}}
{{ namespace="dsws-wm110018376-s",}}
{{ config_file="/app/gitsync/repo/dags/k8s-elr-stage",}}
{{ image="docker.repo1.uhc.com/as/spark-k8s:1.0.0",}}
{{ .}}
{{ .}}
KubernetesPodOperator uses default token for the namespace which, in our env, does not have necessary privileges to create a pod. It fails to use token specified in config_file - in above example, it fails to use {{/app/gitsync/repo/dags/k8s-elr-stage}}
Same occurs when using default kubernetes config in {{${AIRFLOW_HOME}/.kube/config}}
i.e. when {{config_file }}is not specified.
Again, this is not used & airflow uses the default token.
This is a new issue that does not exist in 1.10.6.
was:
Call KubernetesPodOperator and provide kubernetes context via a config_file.
KubernetesPodOperator uses default token for the namespace which, in our env, does not have necessary privileges to create a pod. It fails to use token specified in config_file.
Same occurs when using default kubernetes config in ${AIRFLOW_HOME}/.kube/config
This is a new issue that does not exist in 1.10.6.
> kubernetes_pod_operator no longer using kube context in provided config_file
> ----------------------------------------------------------------------------
>
> Key: AIRFLOW-6618
> URL: https://issues.apache.org/jira/browse/AIRFLOW-6618
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators
> Affects Versions: 1.10.7
> Environment: Airflow on Kubernetes in named namespace (not default namespace) and using a specified token - not default namespace token.
> Reporter: Pat Carroll
> Priority: Major
>
> Call KubernetesPodOperator and provide kubernetes context via a config_file.
> e.g.
> {{doPod = KubernetesPodOperator(}}
> {{ namespace="dsws-wm110018376-s",}}
> {{ config_file="/app/gitsync/repo/dags/k8s-elr-stage",}}
> {{ image="docker.repo1.uhc.com/as/spark-k8s:1.0.0",}}
> {{ .}}
> {{ .}}
> KubernetesPodOperator uses default token for the namespace which, in our env, does not have necessary privileges to create a pod. It fails to use token specified in config_file - in above example, it fails to use {{/app/gitsync/repo/dags/k8s-elr-stage}}
> Same occurs when using default kubernetes config in {{${AIRFLOW_HOME}/.kube/config}}
> i.e. when {{config_file }}is not specified.
> Again, this is not used & airflow uses the default token.
> This is a new issue that does not exist in 1.10.6.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)