fix(core): hide target pod during migration via cilium label #609
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
Isteb4k
force-pushed
the
fix/core/hide-target-pod-during-migration-via-cilium-label
branch
10 times, most recently
from
8b3929e to
9bfd49e
Compare
Signed-off-by: Isteb4k <[email protected]>
Isteb4k
force-pushed
the
fix/core/hide-target-pod-during-migration-via-cilium-label
branch
from
9bfd49e to
6d393da
Compare
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.
Description
During the VM migration process, two pods with the same address are created and packets are randomly delivered to them.
To force delivery of packages to only one VM pod, the special label
network.deckhouse.io/hidden-podfor target pod were added.When the migration completes, the label is removed and the target pod becomes accessible via network.
Checklist