This repository was archived by the owner on Jun 20, 2024. It is now read-only.
Do not exclude k8s node without any IP addr in reclaim #3393
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
bboreham
approved these changes
Sep 5, 2018
|
Should this be on the 2.4 branch? |
Otherwise, such node will be rmpeer'd which can lead to the IPAM inconsistencies "Received update for IP range I own at <..>".
brb
force-pushed
the
issues/3392-get-peers-with-no-ip
branch
from
04ee0de to
acc24f1
Compare
|
Changed the base branch to 2.4. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Otherwise, such node will be rmpeer'd which can lead to the IPAM inconsistencies
"Received update for IP range I own at <..>".Fix #3392 and maybe #3310.