[
https://issues.apache.org/jira/browse/AIRFLOW-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kamil Gałuszka updated AIRFLOW-3937:
------------------------------------
Issue Type: Improvement (was: Bug)
> KubernetesPodOperator
> ---------------------
>
> Key: AIRFLOW-3937
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3937
> Project: Apache Airflow
> Issue Type: Improvement
> Components: kubernetes, operators
> Affects Versions: 1.10.2
> Reporter: Kamil Gałuszka
> Assignee: Kamil Gałuszka
> Priority: Minor
>
> KubernetesPodOperator has basic support for Secret and Configmap, mostly by
> mounting them in files or mounting specific keys in environment variables.
> As for now there is lack of support of just mounting environment variables
> directly through whole k8s Configmap or Secret. Like this:
> {code:java}
> containers:
> -
> name: worker-celery
> image: us.gcr.io/organisation/image-name
> imagePullPolicy: Always
> envFrom:
> - configMapRef:
> name: my-configmap-name
> - secretRef:
> name: my-secret-name
> {code}
> There is very convienient pattern to have secrets and configmaps per image
> that is just attached by k8s to Pod, that should be very useful in Apache
> Airflow.
> As for now I'm aware that there is also in progress AIRFLOW-3381 but it
> solves different problem (still mounting specific keys, rather than whole
> Secret/Configmap), which if Secret/Configmap object has a lot of variables it
> become very inconvenient to add new variable every time it is added to
> Secret/Configmap object.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
