-
Notifications
You must be signed in to change notification settings - Fork 8
Provide a way to deploy new dags from github #6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
it is already done, what is the difference with the current git-sync script and settings in values.yaml? |
How does it currently work? I haven't used git-sync yet but I was expecting to see a sidecar in the deployments that use it like the example in their repo. https://github.com/kubernetes/git-sync/blob/master/demo/config/pod.yaml#L9 |
Read the read me. It is a gitsync launched in the container. Using a sidecar means sharing a folder. Which is also a valid use case |
OK I see it now. Is there a benefit to using this script inside the container vs the sidecar container from the kubernetes org? I thought it was somewhat of an anti-pattern to run more than one process in a container. |
On we need to ensure a share path. If you adapt the conf with an optional sidecar gitsync it can be good to have. |
I see the value |
yes, it does not work anymore, I did not took the time to restore it, and it has many issues that need to be fixed |
It had previously been discussed on slack that we could use the the git-sync sidecar for updating dags from github. The environment variables have already been added. We could add the git-sync sidecar to the scheduler, worker and web deployments. If this is done, do we make it an option in the values.yaml that has to be enabled?
The text was updated successfully, but these errors were encountered: