You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Brandon Clark (Jira)" <ji...@apache.org> on 2020/01/03 03:33:00 UTC

[jira] [Updated] (AIRFLOW-6435) Mount secret files from secrets config

     [ https://issues.apache.org/jira/browse/AIRFLOW-6435?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brandon Clark updated AIRFLOW-6435:
-----------------------------------
    Description: 
There should be a dynamic way to add protected files to pod.  Just as git-sync requires an ssh key to mounted so do other software suites and processes that can be ran from Airflow.

I have created an implementation which requires the following entry in airflow.cfg:
{code:java}

    secret_file_filenames = airflow.pem,client.key
    secret_file_name = airflow
    secret_file_dir = /root/.ssh {code}

  was:There should be a dynamic way to add protected files to pod.  Just as git-sync requires an ssh key to mounted so do other software suites and processes that can be ran from Airflow.


> Mount secret files from secrets config
> --------------------------------------
>
>                 Key: AIRFLOW-6435
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6435
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: executor-kubernetes
>    Affects Versions: 2.0.0, 1.10.8
>            Reporter: Brandon Clark
>            Assignee: Brandon Clark
>            Priority: Major
>              Labels: Kubernetes, executor
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> There should be a dynamic way to add protected files to pod.  Just as git-sync requires an ssh key to mounted so do other software suites and processes that can be ran from Airflow.
> I have created an implementation which requires the following entry in airflow.cfg:
> {code:java}
>     secret_file_filenames = airflow.pem,client.key
>     secret_file_name = airflow
>     secret_file_dir = /root/.ssh {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)