Set up default route for management network for Juniper and Cisco - #740
Open
kraney wants to merge 8 commits into
Open
Set up default route for management network for Juniper and Cisco#740kraney wants to merge 8 commits into
kraney wants to merge 8 commits into
Conversation
kraney
force-pushed
the
juniper-cisco-defaultroute
branch
3 times, most recently
from
August 14, 2026 18:19
32d8cb5 to
fc13495
Compare
bstoll
reviewed
Aug 14, 2026
Have the init container write default route to starting config Juniper and Cisco both ignore the route on eth0 and start from scratch. This uses the initContainer to pick up the route and patch it into the starting config for those types.
kraney
force-pushed
the
juniper-cisco-defaultroute
branch
from
August 15, 2026 00:00
fc13495 to
b553438
Compare
These variables are initialized to a non-zero default, so the check was never successful
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.
Both Juniper and Cisco ignore the K8s-configured settings on eth0 in their container. They set up everything from their own static config, but that makes the management interface unreachable in a multi-node cluster. Setting up the correct routing for the management interface is difficult in a static config since it's different depending on which node the pod has been assigned to at runtime.
This change has KNE update the routing config for the container at runtime to put back the routing set by Kubernetes.