-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add LiveMigrateIfPossible eviction strategy #9798
Conversation
/cc @acardace FYI |
/test all |
f189cde
to
83bad9f
Compare
/cc @davidvossel since you worked lately on an External eviction strategy. |
This strategy will only protect a VM with a PDB if the final determination if a VM is migratable is true. Further the eviction webhook will allow this VM to be evicted instead of migrated in case that the VM is not migratable. Signed-off-by: Roman Mohr <rmohr@google.com>
Signed-off-by: Roman Mohr <rmohr@google.com>
Signed-off-by: Roman Mohr <rmohr@google.com>
83bad9f
to
2463177
Compare
/lgtm |
/retest |
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: xpivarc 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 |
/retest-required |
What this PR does / why we need it:
Add a
LiveMigrateIfPossible
eviction strategy to the KubeVirt CR and VMIs. This strategy makes it easier to express an admin intent on the KubeVirt CR, that in general live-migrations are preferred, but if users do not explicitly request on VMs that they require a live-migration, non-migratable VMs would still just be stopped during evictions.This solves the issue, that right now we would create for non-migratable VMIs a PodDisruptionBudget if the cluster-wide eviction strategy is
LiveMigrate
, leading to to the following two situations:Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #8555
Special notes for your reviewer:
Release note: