You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "jack (JIRA)" <ji...@apache.org> on 2019/06/19 08:35:01 UTC

[jira] [Commented] (AIRFLOW-3274) Add run_as_user and fs_group security context options for KubernetesExecutor

    [ https://issues.apache.org/jira/browse/AIRFLOW-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16867382#comment-16867382 ] 

jack commented on AIRFLOW-3274:
-------------------------------

[~pgag]  do you by any chance plan also to add support for RunAsGroup?

> Add run_as_user and fs_group security context options for KubernetesExecutor
> ----------------------------------------------------------------------------
>
>                 Key: AIRFLOW-3274
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3274
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: executors, scheduler
>            Reporter: Philippe Gagnon
>            Priority: Major
>              Labels: kubernetes
>             Fix For: 1.10.3
>
>
> At this time it is not possible to add `run_as_user` or `fs_group` securityContext options to worker pods when using KubernetesExecutor. This makes it harder to use KubernetesExecutor on clusters with pod security policies which do not allow containers to run as root.
> I have already implemented this functionality for my internal use and will propose a PR soon.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)