Add just
recipe to configure multicluster with a flat network
#11187
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.
Our CI infrastructure does not currently support running two k3d clusters in a flat network for testing purposes. The process of bridging two k3d clusters is quite simple (assuming one node for each cluster). For each node, a network (IP) route has to be added to route to the other node's cluster CIDR.
This change adds a
just
recipe to configure two running clusters to participate in a flat network. Routes are added by executingip route add
in each respective server's docker container. Additionally, to support this, target clusters now run with a different pod CIDR (to ensure there isn't any overlap between the two).Note: also cleaned up the
mc-test
comment since it wasn't showing properly injust --list
, see before and after below.Before
After
Note 2: still has to be wired in CI. At the moment the recipe is not invoked in our pipeline.
To test, run:
And then apply a pod in each cluster (preferably a client/server, I used curl & podinfo). And then try curling the IP address directly. If it's successful, traffic can be routed: