-
Notifications
You must be signed in to change notification settings - Fork 153
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disable VMI migration upon K8s unschedulable taint #823
Disable VMI migration upon K8s unschedulable taint #823
Conversation
/hold Waiting for kubevirt/kubevirt#4012 |
All tests passed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please notice that virtconfig.MigrationsConfigKey is not reconciled so this is enough for new deployment but not for upgrades
@danielBelenky: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
hco-e2e-image-index-aws lane succeeded. |
@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-image-index-azure, ci/prow/hco-e2e-image-index-gcp In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@danielBelenky: The following test failed, say
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/hold cancel |
6d3459b
to
9a3fc2b
Compare
All tests passed |
/cherry-pick release-1.2 |
@tiraboschi: once the present PR merges, I will cherry-pick it on top of release-1.2 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Currently, the default behaviour is to migrate the VMI when a node is tainted with the node.kubernetes.io/unschedulable key. This behaviour is wrong and can be un-expected from the user's perspective because the unschedulable taint means "do not schedule new workloads on this node" and not "evict existing workloads from this node". kubevirt/kubevirt#4012 adds support for the eviction API so we can properly handle node drains and specific evictions on VMI pods. This patch avoid setting (and explicitly removes during upgrades if set in the past) the default node drain key so we won't migrate VMIs when we're not expected to do so. Fixes: https://bugzilla.redhat.com/1881676 Signed-off-by: Daniel Belenky <[email protected]> Signed-off-by: Simone Tiraboschi <[email protected]>
9a3fc2b
to
3c05b7f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nunnatsa The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@danielBelenky: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
hco-e2e-upgrade-prev-azure lane succeeded. |
@hco-bot: Overrode contexts on behalf of hco-bot: ci/prow/hco-e2e-upgrade-prev-aws In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@tiraboschi: #823 failed to apply on top of branch "release-1.2":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Currently, the default behaviour is to migrate the VMI when a node is tainted with the node.kubernetes.io/unschedulable key. This behaviour is wrong and can be un-expected from the user's perspective because the unschedulable taint means "do not schedule new workloads on this node" and not "evict existing workloads from this node". kubevirt/kubevirt#4012 adds support for the eviction API so we can properly handle node drains and specific evictions on VMI pods. This patch avoid setting (and explicitly removes during upgrades if set in the past) the default node drain key so we won't migrate VMIs when we're not expected to do so. Fixes: https://bugzilla.redhat.com/1881676 Signed-off-by: Daniel Belenky <[email protected]> Signed-off-by: Simone Tiraboschi <[email protected]> Co-authored-by: Daniel Belenky <[email protected]>
Currently, the default behaviour is to migrate the VMI when a node is
tainted with the node.kubernetes.io/unschedulable key. This behaviour is
wrong and can be un-expected from the user's perspective because the
unschedulable taint means "do not schedule new workloads on this node"
and not "evict existing workloads from this node".
kubevirt/kubevirt#4012 adds support for the
eviction API so we can properly handle node drains and specific
evictions on VMI pods.
This patch avoid setting (and explicitly removes during upgrades if
set in the past) the default node drain key so we won't migrate VMIs
when we're not expected to do so.
Fixes: https://bugzilla.redhat.com/1881676
Signed-off-by: Daniel Belenky [email protected]
Release note: