-
Notifications
You must be signed in to change notification settings - Fork 98
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
Fix initContainer failure during pod restart #337
Conversation
This fix resolved the error in my environment, but I'm not sure which tests are required to validate it. I'm also unsure how files were created on the EmptyDir before init. Possibly a successful init previously, then a restart on the same node. |
@pl4nty thanks for the PR! Instead of adding |
Thanks @kate-osborn, how's this? Just removes the stale config if present. I've tested successfully on my dev cluster |
LGTM! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @pl4nty
There is a small problem in the script -- please see the review comment with the fix suggestion.
Could you also rebase your branch against the latest main?
@pl4nty the commit history on this PR has several commits from the main branch which is making the diff incorrect. Can you do an interactive rebase on main and squash all the commits into a single commit? That should fix the diff. Thanks! |
@kate-osborn apologies, I was away for a while. Thanks for your patience! |
Proposed changes
The gateway initContainer fails when creating folders on the config volume, if they already exist:
This failure prevents the gateway from starting. This PR adds a
mkdir
flag to ignore the error and skip folder creation if the folders already exist.Checklist
Before creating a PR, run through this checklist and mark each as complete.