mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-22 04:33:36 +09:00
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 <f@lex.la>