WIP: When using subnet discovery, you can disable the primary subnet with kubernetes.io/role/cni=0 #3121
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.
What type of PR is this? feature
Which issue does this PR fix?: part of #3067
What does this PR do / Why do we need it?:
On initialization we check if the primary subnet is tagged with kubernetes.io/role/cni = 0 and we skip to other subnet for IP adressing.
Testing done on this change: Build on local and deploy on cluster, haven't tested all possibilities yet.
Will this PR introduce any new dependencies?: None
Will this break upgrades or downgrades? Has updating a running cluster been tested?: It was tested, there is a warning that should be posted that the value 0 now disable the feature.
Does this change require updates to the CNI daemonset config files to work?: No
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.