You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Aizhamal Nurmamat kyzy (JIRA)" <ji...@apache.org> on 2019/05/18 03:07:00 UTC
[jira] [Updated] (AIRFLOW-3443) KubernetesPodOperator
image_pull_secrets must be a valid parameter
[ https://issues.apache.org/jira/browse/AIRFLOW-3443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aizhamal Nurmamat kyzy updated AIRFLOW-3443:
--------------------------------------------
Component/s: (was: kubernetes)
operators
> KubernetesPodOperator image_pull_secrets must be a valid parameter
> ------------------------------------------------------------------
>
> Key: AIRFLOW-3443
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3443
> Project: Apache Airflow
> Issue Type: Bug
> Components: operators
> Affects Versions: 1.10.1
> Reporter: Maxime Rauer
> Assignee: Maxime Rauer
> Priority: Blocker
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> We've been successfully using the KubernetesPodOperator in our company with a local Docker registry, but when switching to a private repository such as Amazon ECR, Airflow wasn't able to pull the secrets from the cluster.
> I have made a change in the *make_pod()* function on *kubernetes_pod_operator.py* to support a new *image_pull_secrets* field.
> This works great on our end, and the community could benefit from it for the version 10.0.1
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)