From 63b91775411328f30cd62146ebb4ff373a80d8e7 Mon Sep 17 00:00:00 2001 From: Kaxil Naik Date: Tue, 14 Jul 2020 20:27:25 +0100 Subject: [PATCH] Add note in Updating.md about the change in `run_as_user` default 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` --- UPDATING.md | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/UPDATING.md b/UPDATING.md index a24f0bf5c0bde..ead3aed8e2910 100644 --- a/UPDATING.md +++ b/UPDATING.md @@ -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