-
Notifications
You must be signed in to change notification settings - Fork 3
Closed
Labels
area/networkingNetworking-related tasks and improvements.Networking-related tasks and improvements.bugSomething isn't workingSomething isn't working
Milestone
Description
Describe the bug
Ironcore Network peering status keeps getting flapped when external peering controller is used
To Reproduce
- Create 2 Network with peering configuration.
- Set disalbleNetwrokPeering to false for metalnetlet.
- Use external peering-controller to handle peering.
- Observer when external peering controller is updating peering status of Ironcore
Network, apinetlet is reversing back with old status.
Expected behavior
APINetlet should not update peering status if external peering controller is used.
A flag should be introduced like in metalnetlet, to indicate apinetlet to not to update peering status if external controller is used.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
APINetlet tries to comparing peering status with Ironcore's status even though external controller is handling peering.
This make external peering controller trigger recursive reconcile loops for Ironcre Network.
Metadata
Metadata
Assignees
Labels
area/networkingNetworking-related tasks and improvements.Networking-related tasks and improvements.bugSomething isn't workingSomething isn't working