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

Support running MetalLB and IPV6 #4131

Closed
tssurya opened this issue Feb 6, 2024 · 1 comment · Fixed by #4201 or #4205
Closed

Support running MetalLB and IPV6 #4131

tssurya opened this issue Feb 6, 2024 · 1 comment · Fixed by #4201 or #4205
Labels
ci-ipv6 Add support for IPV6 e2e's to run upstream

Comments

@tssurya
Copy link
Member

tssurya commented Feb 6, 2024

For both shared and local gateway we use metalLB to provision load balancer IPs on kind. There are some specific hacks we do like adding routes between docker containers to make this work. This is currently not considering IPV6. Add support for this.

Currently the services+MetalLB tests are being skipped as part of #4106 where we are adding 3 new IPV6 lanes:

  1. Control Plane, shared, IPV6, IC
  2. Control Plane, local, IPV6, IC
  3. Control Plane, shared, IPV6, nonIC

Goal: Troubleshoot with IPV6 KIND and fix it and re-enable the tests

@tssurya tssurya added the ci-ipv6 Add support for IPV6 e2e's to run upstream label Feb 6, 2024
@kyrtapz
Copy link
Contributor

kyrtapz commented Mar 12, 2024

Fixed with:
#4201
#4205

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-ipv6 Add support for IPV6 e2e's to run upstream
Projects
None yet
2 participants