Fix additional volumes in MirrorMaker 2 #11022
Merged
+68
−34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of change
Description
The additional volume mounts in MirrorMaker 2 deployments are currently added twice to the list because they are already inherited from the underlying Connect cluster. As a result, when you try to use them, the Pods fail to create with the following error:
This Pr fixes it and makes sure they are added only once. It also fixes the tests to properly check the full volume list and not just check a presence of individual volume which helped to cover this bug in the unit tests.
This was raised by #11002.
This should be backported to the 0.45.0 branch.
Checklist