Implement EVPN Fabric loopback reconciliation#353
Open
felix-kaestner wants to merge 1 commit into
Open
Conversation
hardikdr
added
the
area/switch-automation
felix-kaestner
force-pushed
the
fabric-loopbacks
branch
from
May 18, 2026 07:28
45df664 to
d252c82
Compare
|
This PR is stale because it has been open for 45 days with no activity. |
felix-kaestner
force-pushed
the
fabric-crd
branch
from
July 14, 2026 15:40
a73a136 to
b374fc8
Compare
felix-kaestner
force-pushed
the
fabric-loopbacks
branch
from
July 14, 2026 15:40
d252c82 to
41bfb4f
Compare
felix-kaestner
force-pushed
the
fabric-crd
branch
2 times, most recently
from
July 16, 2026 13:52
62d1fb2 to
f7bd981
Compare
Reconcile lo0 (Router-ID), lo1/lo2 (VTEP), and lo100 (anycast RP) loopback Claims and Interfaces for all fabric devices. The Fabric becomes the controller owner of each Claim so the Owns() watch re-enqueues correctly. Interfaces are only created once the Claim is allocated; a guard at the top of Reconcile short-circuits when the provider does not implement InterfaceProvider. Extend provider interface with LoopbackInterfaceName so each driver can return a vendor-specific handle for a given loopback index. Add envtest suite covering Claims, Interfaces, ownership, and the Ready condition. Signed-off-by: Felix Kästner <felix.kaestner@sap.com>
felix-kaestner
force-pushed
the
fabric-crd
branch
from
July 16, 2026 14:24
863564f to
0146260
Compare
felix-kaestner
force-pushed
the
fabric-loopbacks
branch
from
July 23, 2026 15:01
41bfb4f to
7d67cb2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reconcile lo0 (Router-ID), lo1/lo2 (VTEP), and lo100 (anycast RP) loopback Claims and Interfaces for all fabric devices. The Fabric becomes the controller owner of each Claim so the Owns() watch re-enqueues correctly. Interfaces are only created once the Claim is allocated; a guard at the top of Reconcile short-circuits when the provider does not implement InterfaceProvider.
Extend provider interface with LoopbackInterfaceName so each driver can return a vendor-specific handle for a given loopback index.
Add envtest suite covering Claims, Interfaces, ownership, and the Ready condition.