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

Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/05/03 02:49:43 UTC

[GitHub] [airflow] aneesh-joseph opened a new issue #8683: fs_group is being defaulted to 0 while using kubernetes executor and airflow 1.10.10

aneesh-joseph opened a new issue #8683:
URL: https://github.com/apache/airflow/issues/8683

<!--

Welcome to Apache Airflow! For a smooth issue process, try to answer the following questions.
Don't worry if they're not all applicable; just try to include what you can :-)

If you need to include code snippets or logs, please put them in fenced code
blocks. If they're super-long, please use the details tag like
<details><summary>super-long log</summary> lots of stuff </details>

Please delete these comment blocks before submitting the issue.

-->

<!--

IMPORTANT!!!

PLEASE CHECK "SIMILAR TO X EXISTING ISSUES" OPTION IF VISIBLE
NEXT TO "SUBMIT NEW ISSUE" BUTTON!!!

PLEASE CHECK IF THIS ISSUE HAS BEEN REPORTED PREVIOUSLY USING SEARCH!!!

Please complete the next sections or the issue will be closed.
This questions are the first thing we need to know to understand the context.

-->

**Apache Airflow version**: 1.10.10

**Kubernetes version (if you are using kubernetes)** (use `kubectl version`): Not version specific

**Environment**:

- **Cloud provider or hardware configuration**:
- **OS** (e.g. from /etc/os-release):
- **Kernel** (e.g. `uname -a`):
- **Install tools**:
- **Others**:

**What you expected to happen**:

If I use the `KubernetesExecutor` and do not set a `fs_group` in airflow.cfg I would expect that the the `fs_group` is not set in the securityContext while creating the pod..It is also expected that the `fs_group` is set to 65533 if git sync with ssh is being used and `fs_group` is not explicitly set..

**What happened**:

If `fs_group` is not set, it gets defaulted to 0 - https://github.com/apache/airflow/blob/1.10.10/airflow/contrib/executors/kubernetes_executor.py#L295-L300 . Since this is being defaulted to 0, the logic to set it to 65533
doesn't seem to come into play https://github.com/apache/airflow/blob/1.10.10/airflow/contrib/kubernetes/worker_configuration.py#L238-L239

**How to reproduce it**:

Remove `fs_group` config from airflow.cfg and examine the worker pods created by KubernetesExecutor using `kubectl get pod <worker_pod_name> -o` and examine the securityContext,
<!---

As minimally and precisely as possible. Keep in mind we do not have access to your cluster or dags.

If you are using kubernetes, please attempt to recreate the issue using minikube or kind.

## Install minikube/kind

- Minikube https://minikube.sigs.k8s.io/docs/start/
- Kind https://kind.sigs.k8s.io/docs/user/quick-start/

If this is a UI bug, please provide a screenshot of the bug or a link to a youtube video of the bug in action

You can include images using the .md sytle of
![alt text](http://url/to/img.png)

To record a screencast, mac users can use QuickTime and then create an unlisted youtube video with the resulting .mov file.

--->

**Anything else we need to know**:

<!--

How often does this problem occur? Once? Every time etc?

Any relevant logs to include? Put them here in side a detail tag:
<details><summary>x.log</summary> lots of stuff </details>

-->

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org