Skip to content
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

Remove custom Docker networks from integration tests #3602

Merged
merged 1 commit into from
Oct 18, 2023

Conversation

twz123
Copy link
Member

@twz123 twz123 commented Oct 18, 2023

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

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update

How Has This Been Tested?

  • Manual test
  • Auto test added

Checklist:

  • My code follows the style guidelines of this project
  • My commit messages are signed-off
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my code and corrected any misspellings

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.

Signed-off-by: Tom Wieczorek <[email protected]>
@twz123 twz123 added bug Something isn't working area/smoke-tests labels Oct 18, 2023
@twz123 twz123 requested a review from a team as a code owner October 18, 2023 16:20
@twz123 twz123 requested review from kke and makhov October 18, 2023 16:20
@twz123 twz123 mentioned this pull request Oct 18, 2023
16 tasks
Copy link
Member

@jnummelin jnummelin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@twz123 twz123 merged commit b0ef86b into k0sproject:main Oct 18, 2023
73 checks passed
@twz123 twz123 deleted the inttest-remove-docker-networks branch October 18, 2023 18:06
juanluisvaladas added a commit to juanluisvaladas/k0s that referenced this pull request Sep 2, 2024
Custom docker networks were removed in k0sproject#3602 because the custom networks
were revealing issues in our test suite.

This effectively means k0smotron cannot bump the k0s dependency to a
newer version.

This is a partial revert of 57b5560 getting only the minimum subset that
we require for k0smotron.

Signed-off-by: Juan-Luis de Sousa-Valadas Castaño <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/smoke-tests bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants