Support defining default routes (including dummy ones) for compute nodes via cloud-init #539
Conversation
This file contains 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
sjpb
force-pushed
the
feat/cloudinit-gateways
branch
from
eb2e92c to
5542656
Compare
…-slurm-appliance into feat/cloudinit-gateways
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
All nodes need a default route so k3s can identify the primary IP. This can be hard to do via subet gateways for clusters with some multi-homed nodes. This PR adds tofu compute group parameters
gateway_nmcli_connectionandgateway_ipwhich allow defining default routes for compute nodes via cloud-init to work around this.