You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/05/14 20:00:00 UTC
[jira] [Commented] (AIRFLOW-2460) KubernetesPodOperator should be
able to attach to volume mounts and configmaps
[ https://issues.apache.org/jira/browse/AIRFLOW-2460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16474731#comment-16474731 ]
ASF subversion and git services commented on AIRFLOW-2460:
----------------------------------------------------------
Commit 0b6a7000c063d8bf744a1b907f4e1d7c04f57e57 in incubator-airflow's branch refs/heads/master from [~dimberman]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=0b6a700 ]
[AIRFLOW-2460] Users can now use volume mounts and volumes when
launching pods using k8s operator
Closes #3356 from dimberman/k8s-mounts
> KubernetesPodOperator should be able to attach to volume mounts and configmaps
> ------------------------------------------------------------------------------
>
> Key: AIRFLOW-2460
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2460
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Daniel Imberman
> Assignee: Daniel Imberman
> Priority: Major
> Fix For: 1.10.0, 2.0.0
>
>
> In order to run tasks using the KubernetesPodOperator in a production setting, users need to be able to access pre-existing data through PersistentVolumes or ConfigMaps.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)