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
L2-announcements lack ipv6-support #28985
Comments
/cc @dylandreimerink Not sure if this falls under sig/agent or sig/datapath. |
Both, to implement this we need to add
|
This issue has been automatically marked as stale because it has not |
Is there any news regarding this issue? I do not think it should go stale. |
Let me pin this issue. Also, contribution is appreciated. |
It is only used when L2 announcements are enabled, which are not, due to this bug: cilium/cilium#28985
Any ETA for this? |
This issue has no assignee, which means that nobody is working on this issue at the moment and there is no ETA. As Yutaro mentioned, contributions are appreciated. |
Is your proposed feature related to a problem?
Yes, I do not want to use MetalLB when using the Cilium-network stack in k8s. When using Cilium's L2-announcements, it seems very pointless to use MetalLB additionally in this scenario just for ipv6.(then I could drop L2-announcements all-together and use MetalLB instead)
Describe the feature you'd like
One of the following limitations of L2-announcements states the following:
Is there any way to assign somebody to fix this? This would lead to a lot of people dropping using MetalLB(me included).
The text was updated successfully, but these errors were encountered: