potiuk commented on issue #27476: URL: https://github.com/apache/airflow/issues/27476#issuecomment-1305765973
> In the article you mentioned, there is no even a single reference to Kubernetes. In the Kubernetes ecosystem this is the way to share files between pods (git-sync runs on the scheduler pod, webserver pod and worker pods). Using persistent volumes is **one** of the ways to synchronise files between pods. But it is by far not the only one. This is why git-sync was invented - to provide alternative. And the article IS all about K8S. Git-Sync is in fact K8s project https://github.com/kubernetes/git-sync project that allows you to sync files to all components WITHOUT persistency. Persistency is really only useful when you do not use any other mechanism. And if you are running git-sync for all the components, there is absolutely no need to **again** synchronize them via persisttent storage. Why do you want to do htat? * You already have all the files synced with git-sync. * All components get the files synced and they have their own identical copy of all files in your DAG folder * Why do you need to add persistency on top of it ? What does it give you additionally to git-synced files? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
