Closed weizhoublue closed 11 months ago
热迁移前后
迁移中
~# kubectl get VirtualMachineInstanceMigration -o wide
NAME PHASE VMI
kubevirt-migrate-vm-6wgr7 Scheduling vm-migration
~# kubectl get vm
NAME AGE STATUS READY
vm-migration 117s Running True
~# kubectl get vmi
NAME AGE PHASE IP NODENAME READY
vm-migration 113s Running 172.21.175.14 kubevirt-worker True
~# kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE
virt-launcher-vm-migration-lv7h8 2/2 Running 0 2m15s 172.21.175.14 kubevirt-worker <none> 1/1
virt-launcher-vm-migration-rmqvm 0/2 Init:1/2 0 52s 172.21.18.159 kubevirt-control-plane <none> 0/1
迁移接近完成时,两个pod 都是 running
迁移完成
~# kubectl get VirtualMachineInstanceMigration -o wide
NAME PHASE VMI
kubevirt-migrate-vm-swckv Succeeded vm-migration
~# kubectl get vmi
NAME AGE PHASE IP NODENAME READY
vm-migration 147m Running 172.21.18.160 kubevirt-control-plane True
老 pod 一致处于 Completed 状态
~# kubectl get pod -o wide
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
virt-launcher-vm-migration-g89xw 2/2 Running 0 4h6m 172.21.18.160 kubevirt-control-plane <none> 1/1
virt-launcher-vm-migration-lv7h8 0/2 Completed 0 4h44m 172.21.175.14 kubevirt-worker <none> 1/1
问题:在迁移过程中,2个pod 都是同时 running 的时间,分配固定 IP 就要在 老pod 还未 Completed 就把 IP 分配新POD使用,这样短暂瞬间 是否会出问题 ? 并且 这个瞬间 会因为 新pod arping 失败 而 启动失败,如何解决 ?
固定IP 支持 热迁移 比较麻烦
vmi and its vm pod
VM pod
restart vm
思路: endpoint: (1) kubevirt: true (2) vmi: uuid (3) pod: uuid
list 监控 VMI 删除事件,是否 ippool 中的 IP