-
Notifications
You must be signed in to change notification settings - Fork 8
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
wrapping gitpuller #267
Comments
Based on response to this discourse post, there is no easy fix. Plan going forward:
|
@kcranston just an idea - is it possible to send an email or message somehow when this fails? that may be difficult i just figured i'd ask. this could even be writing a message on github in an issue and tagging X people. i agree it's useful to allow the pod to start! it's also useful for me to know there is a point of failure when it happens. |
i mention this only because i know we use the github API and as such i was wondering if adding to an issue or creating an issue is something we could do via python too! just an idea. maybe a bad one... or a complicated one? but an idea. |
I like this idea. Let me think about options. |
Some notes here about wrapping gitpuller to deal with #255 and #205
lifecycleHook
and if it fails, the pod does not start. We can't fix the failure by cleaning up the file system because we can't access the unmounted volume for a pod that isn't runningThe text was updated successfully, but these errors were encountered: