Fixing default table route management to work in all dual-stack cases #205
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.
A dual-stack network can include both IPv4 and V6 CIDRs, allocation pools, and IP routes.
But not every Pod connecting to a DS network will have DS interfaces.
So, IP routes need to be selectively created; only if an IP was really assigned to the iterface from its respective domain.
Otherwise Linux throws a "no route to host" error during route creation, which in turn fails Pod instantiation.