[
https://issues.apache.org/jira/browse/AIRFLOW-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16874084#comment-16874084
]
ASF subversion and git services commented on AIRFLOW-4845:
----------------------------------------------------------
Commit c47d215d70393e4ff9c708db10b039f53bdac801 in airflow's branch
refs/heads/v1-10-stable from George Miller
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=c47d215 ]
[AIRFLOW-4845] Fix bug where runAsUser 0 doesn't get set in k8s security
context (#5474)
(cherry picked from commit 2bf4fe3bc8a9c522d1a1df521f8f502e576a7ccc)
> Kubernetes Executor Run As User 0 does not work
> -----------------------------------------------
>
> Key: AIRFLOW-4845
> URL: https://issues.apache.org/jira/browse/AIRFLOW-4845
> Project: Apache Airflow
> Issue Type: Bug
> Components: executors
> Affects Versions: 1.10.4
> Reporter: George Miller
> Assignee: George Miller
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.10.4
>
>
> If I set run_as_user in the kubernetes section of airflow.cfg to 0, that does
> not get applied. The problem is this code
> ```
> if self.kube_config.worker_run_as_user:
> security_context['runAsUser'] = self.kube_config.worker_run_as_user
> ```
> if self.kube_config.worker_run_as_user is an int 0, that get implied as a
> False and thus the security context never gets set. This also happens to
> fsGroup. A small change needs to be made to make this check against a ""
> (empty string) as that's what it's defaulted to in the default airflow config
> file.
>
> Here is my pr [https://github.com/apache/airflow/pull/5474]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
