Skip to content
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.

Sign up for GitHub

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

Fix HCOMisconfiguredDescheduler lines length #276

Merged
merged 1 commit into from
Dec 25, 2024
Merged

Fix HCOMisconfiguredDescheduler lines length #276

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions docs/runbooks/HCOMisconfiguredDescheduler.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,8 @@ and a live migration takes time to perform.
Therefore, when a `virt-launcher` pod is migrating to another node in the background,
the descheduler detects this as a pod that failed to be evicted. As a consequence,
the manner in which KubeVirt handles eviction requests causes the descheduler
to make incorrect decisions and take incorrect actions that might destabilize the cluster.
to make incorrect decisions and take incorrect actions that might
destabilize the cluster.

To correctly handle the special case of an evicted VM pod triggering a live
migration to another node, the `Kube Descheduler Operator` introduced
Expand Down Expand Up @@ -44,8 +45,8 @@ to unstable or unpredictable behavior, which negatively impacts cluster stabilit
devEnableEvictionsInBackground: true
```

If these lines are not present, the `Kube Descheduler Operator` is not correctly configured
to work alongside KubeVirt.
If these lines are not present, the `Kube Descheduler Operator` is not correctly
configured to work alongside KubeVirt.

## Mitigation

Expand Down
Loading