You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, it's not possible to use link-local addresses for building BGP peering, since there is no ability to specify interface where peer can be found. Value e.g. fe80::xxxx:xxxx:xxxx:xxxx%enp1s0 for peerAddress in BGPPeer rejected with the error Error from server (Forbidden): error when creating "metlb-conf.yaml": admission webhook "bgppeersvalidationwebhook.metallb.io" denied the request: parsing peer gk-peer-v6: invalid BGPPeer address "fe80::b8a3:17ff:fe0c:c54a%enp1s0"
interface string
Define interface we should use for link-local BGP IPv6 sessions. Interface can also be specified
as a part of neighbor address (e.g., neighbor fe80::1234%eth0 as 65000;).
Is your feature request related to a problem?
At the moment, it's not possible to use link-local addresses for building BGP peering, since there is no ability to specify interface where peer can be found. Value e.g.
fe80::xxxx:xxxx:xxxx:xxxx%enp1s0
forpeerAddress
inBGPPeer
rejected with the errorError from server (Forbidden): error when creating "metlb-conf.yaml": admission webhook "bgppeersvalidationwebhook.metallb.io" denied the request: parsing peer gk-peer-v6: invalid BGPPeer address "fe80::b8a3:17ff:fe0c:c54a%enp1s0"
Describe the solution you'd like
This is already supported by FRR:
and the second line of the config above (interface specification) can be generated based on the following BGPPeer specification:
Additional context
This change will allow to use any available addressing in IPv6 environment, including link-local addresses.
There was a discussion here about this - https://kubernetes.slack.com/archives/C8FSTGU56/p1717574500705649
I've read and agree with the following
The text was updated successfully, but these errors were encountered: