-
Notifications
You must be signed in to change notification settings - Fork 455
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
limit bgp announcements #3211
Comments
@KillMaster9 could you please take a look at this and #3212 |
Hi, as example calico uses blocksize parameter in order not to announce only /32 addresses but optimise in /26 default prefixes https://docs.tigera.io/calico/latest/reference/resources/ippool This optimization may affect the ipam functionality too. |
|
|
Similar to k8s service, can set a TrafficPolicy attribute. If it is Local, only the Pod resources of this node can be published. If it is Cluster, all Pod resources can be published. The default is Cluster. The Metallb also expanded this function. @oilbeater |
Hi @KillMaster9 , can you please provide an example how to set this filtering? i may give a try now. i could only find https://kubernetes.io/docs/concepts/services-networking/service-traffic-policy/ refering to Service definition, not pods. thank you |
Expected Behavior
each worker announces only its hosted pods
Actual Behavior
in a Layer3 scenario, where workers are deployed on different L3 networks, when BGP speakers are enabled they announce all the nets/pods without any possibility to filter on availability zone or worker containers.
This create problems on upstream connectivity because of asymmetrical routing
Steps to Reproduce the Problem
Additional Info
Kubernetes version: 1.28
kube-ovn version: 1.11.10
The text was updated successfully, but these errors were encountered: