[
https://issues.apache.org/jira/browse/AIRFLOW-3274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16811312#comment-16811312
]
ASF subversion and git services commented on AIRFLOW-3274:
----------------------------------------------------------
Commit be20160f88d8d4ea858d989cd0868004eb9e65de in airflow's branch
refs/heads/v1-10-test from Philippe Gagnon
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=be20160 ]
[AIRFLOW-3274] Add run_as_user and fs_group options for Kubernetes (#4648)
> 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: kubernetes, scheduler
> Reporter: Philippe Gagnon
> Priority: Major
> 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)
