Remove custom Docker networks from integration tests #3602
Merged
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.
Description
Using custom networks makes CoreDNS's loop plugin detect a loop and fail. Fix this by simply ripping out all custom network functionality from the inttests. An alternative would have been to apply the workarounds in k0s's Docker entrypoint also inside the inttests, but, since the custom networks apparently didn't serve any special purpose, deleting code is better than adding code.
Type of change
How Has This Been Tested?
Checklist: