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/22 15:16:00 UTC
[jira] [Created] (AIRFLOW-6618) kubernetes_pod_operator no longer
using kube context in provided config_file
Pat Carroll created AIRFLOW-6618:
------------------------------------
Summary: 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
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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)