This repository was archived by the owner on Dec 7, 2023. It is now read-only.
Change default CNI network name, bridge name, and subnet #460
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.
Fixes #424
Fixes #455
The solution in this patch for #424 is to use a static subnet in the 10.0.0.0/8 range.
This avoids the complexity of collaborating with the docker defaulting logic which requires calculating and iterating a over a similar list of subnets and checking to see if they're in use by the kernel.
This:
Rationale for the subnet choice is documented on the constant.
Changing these CNI details will ultimately necessitate that any current users of our (mostly broken) default CNI setup will likely want to migrate.
This is not forced on users though. The config is still only written when the CNI net conf dir is empty.