Skip to content

Commit

Permalink
Add note in Updating.md about the change in run_as_user default (#9…
Browse files Browse the repository at this point in the history
…822)

Until Airflow 1.10.10 the default run_as_user config (https://airflow.readthedocs.io/en/1.10.10/configurations-ref.html#run-as-user) which defaulted it to root user `0` (https://github.com/apache/airflow/blob/96697180d79bfc90f6964a8e99f9dd441789177c/airflow/contrib/executors/kubernetes_executor.py#L295-L301)

In Airflow 1.10.11 we changed it to `50000`

GitOrigin-RevId: ea0d2749cf9eda3c90e293c6a42489cb587aa7b8
  • Loading branch information
kaxil authored and Cloud Composer Team committed Sep 12, 2024
1 parent b7a33a1 commit 52096f8
Showing 1 changed file with 22 additions and 0 deletions.
22 changes: 22 additions & 0 deletions UPDATING.md
Original file line number Diff line number Diff line change
Expand Up @@ -1476,6 +1476,28 @@ auth_backend = airflow.api.auth.backend.default
Since XCom values can contain pickled data, we would no longer allow adding or
changing XCom values from the UI.

### Default for `run_as_user` configured has been changed to 50000 from 0

The UID to run the first process of the Worker PODs when using has been changed to `50000`
from the previous default of `0`. The previous default was an empty string but the code used `0` if it was
empty string.

**Before**:

```ini
[kubernetes]
run_as_user =
```

**After**:

```ini
[kubernetes]
run_as_user = 50000
```

This is done to avoid running the container as `root` user.

## Airflow 1.10.10

### Setting Empty string to a Airflow Variable will return an empty string
Expand Down

0 comments on commit 52096f8

Please sign in to comment.