Clone git repo as airflow user instead of root about charts HOT 4 CLOSED

@DavidChenLondon can you provide a basic example of something which fails?

from charts.

Hi @thesuperzapper According to https://github.com/airflow-helm/charts/tree/main/charts/airflow#option-1---git-sidecar-recommended , our ML repo will be cloned as "root" user, but the worker will be running as "airflow" user, thus, this would cause file permission issue if we try to write some files under our ML repo source code directory, so we have to write to other writable directory instead (e.g. /tmp). A possible solution is securityContext.runAsUser, I'm still new to kubernetes, it would be helpful if other experienced people solve this issue. Thanks

from charts.

@DavidChenLondon this is intended behaviour, you shouldn't be writing to the dag folder

There are a few reasons for this:

1. if we let you write, you would make the folder out of sync with the other workers/scheduler pods
2. the sync script will remove your files at the next sync anyway, see the script here

from charts.

@thesuperzapper thanks, the logic behind makes sense. We moved all our temporary ML/ETL data into /tmp.

from charts.