-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
vendor: Update go.universe.tf/metallb #16523
Conversation
Following cilium/metallb#4, Cilium is now tracking the code from the v0.9.6 branch of cilium/metallb: https://github.com/cilium/metallb/tree/v0.9.6 This was done in a backwards-compatible way to ensure that older versions of Cilium can still build by avoiding the invalidation of the previous commit SHA (40d425d20241). Signed-off-by: Chris Tarazi <chris@isovalent.com>
test-only --focus="K8sServicesTest.*Connectivity to endpoint via LB" --k8s_version=1.21 --kernel_version=net-next Edit: This is the only test needed to validate MetalLB is working |
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.
I really hope that our patches get upstreamed so that we can get rid of this replace directive.
@rolinh It is on my to-do list, it will get done :) |
test-only --focus="K8sServicesTest.*Connectivity to endpoint via LB" --k8s_version=1.21 --kernel_version=net-next Edit: Passed |
Following cilium/metallb#4, Cilium is now
tracking the code from the v0.9.6 branch of cilium/metallb:
https://github.com/cilium/metallb/tree/v0.9.6
This was done in a backwards-compatible way to ensure that older
versions of Cilium can still build by avoiding the invalidation of the
previous commit SHA (40d425d20241).
Signed-off-by: Chris Tarazi chris@isovalent.com