-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Re-run initContainers in a Deployment when containers exit on error #871
Comments
A PR still needs to be created for this proposal. If someone else is passionate about this issue, I'm happy to hand off, but I'll continue to pursue it and am currently working on a PR for the enhancements file. This proposal follows up on an issue that was closed because it was expected to be solved under a different KEP. I see two potential solutions to this problem. Drawbacks and concerns in regard to option a. were discussed in the issue linked to above. |
/assign @majgis |
I have some questions about the intended design. Would rerunning initContainers on container exit perform a different action that is different from what initContainer would do on startup? |
Hello @majgis , 1.17 Enhancement Shadow here! 🙂 I wanted to reach out to see if this enhancement will be graduating to alpha/beta/stable in 1.17?
Thank you! 🔔Friendly Reminder
|
I'm unable to contribute at this time. I'm closing the issue to step down. Sorry for the noise and not following through. It was a much desired feature where I worked previously. Anyone still anticipating and willig to carry the torch can reopen or start with a new issue. |
Enhancement Description
Re-run initContainers in a Deployment when containers exit on error
TBD
TBD
/sig apps
/sig node
TBD
Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement
The text was updated successfully, but these errors were encountered: