Repository navigation
Commit 46674f8
committed
docs(kubevirt): state the preconditions of the eviction comments
The comments on evictionStrategy and workloadUpdateMethods described
the new behaviour as if it applied to every VMI. The VMI mutator stamps
the cluster strategy into the spec at creation, so a VMI started before
LiveMigrateIfPossible keeps LiveMigrate: if it cannot migrate, its
drain still blocks and the workload updater's eviction is refused until
its VM restarts.
The worker case pointed at the wrong mechanism too. CAPK reports a
non-migratable VMI under evacuation as a terminal failure, and every
kubernetes-nodes group has a MachineHealthCheck, so the Machine gets
replaced. Where maxUnhealthy holds remediation back the VM restarts in
place, but the failure is never cleared, so the Machine is still
replaced later.
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <[email protected]>1 parent 76b3652 commit 46674f8
1 file changed
Lines changed: 10 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
123 | 123 | | |
124 | 124 | | |
125 | 125 | | |
126 | | - | |
| 126 | + | |
127 | 127 | | |
128 | 128 | | |
129 | 129 | | |
130 | 130 | | |
131 | | - | |
132 | | - | |
133 | | - | |
134 | | - | |
135 | | - | |
| 131 | + | |
| 132 | + | |
| 133 | + | |
| 134 | + | |
| 135 | + | |
| 136 | + | |
| 137 | + | |
| 138 | + | |
| 139 | + | |
136 | 140 | | |
137 | 141 | | |
138 | 142 | | |
| |||
0 commit comments