fix(vm): manage pods network priority during a migration using the cilium label #642
+336
−93
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
Manage pods network priority during a migration using the cilium label
Why do we need it, and what problem does it solve?
During the VM migration process, two pods with the same address are created and packets are randomly delivered to them.
Solution:
To force delivery of packages to only one VM pod, the special label
network.deckhouse.io/pod-common-ip-priority
were added.The label allows setting the priority of pod for cilium relative to other pods with the same IP address.
Network traffic will be directed to the pod with the higher priority. Absence of the label means default network behavior:
low
<no label
<high
.How does it work?
What is the expected result?
Packets are delivered as expected: initially only to the source pod during migration, and after migration completes, only to the target pod.
Checklist
Changelog entries