-
Notifications
You must be signed in to change notification settings - Fork 76
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: don't merge volume mount on sidecar container if it exists #6
Conversation
Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! 😄 |
i agreed with cla/licenses |
@bnadim thanks for the PR! If you click through that link (https://yahoocla.herokuapp.com/), the CLA bot should update this PR with your acceptance. Great catch on this :) |
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.
Awesome catch! Would you mind adding a test case that illustrates this behavior? (i.e. a pod with a VolumeMount "foo" does not have its volume replaced by a sidecar injector volumemount config "foo")
cc @iwilltry42 FYI |
Thanks for the PR @bnadim , I actually saw this happening as well (only that for me, the pods wouldn't even be launched, so I couldn't see any error messages). Looks like a stupid autocomplete mistake from my side. Now I can scratch this from my TODO-List, thank you :) @byxorna , thanks for pinging me 👍 |
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.
Looks like VSCode's autocomplete failed me there, thanks for catching that error 👍
Hey @bnadim, mind clicking through the linked |
It should be working now |
@bnadim thank you! merging :) |
What and why?
Adding the same volume mounts to sidecar container and to all containers would end up in an error telling that the volume mounts already exist.
Testing Steps
Using this configuration map we would end up getting the error
Reviewers
Required reviewers:
@byxorna
Request reviews from other people you want to review this PR in the "Reviewers" section on the right.