Myasnikov Daniil a115745c69 feat(vm-disk): let the operator defer binding to the consumer ...

Immediate binding for every source fixed a real bug: a standalone disk
on a WaitForFirstConsumer class has no consumer to wait for, so it never
populated. It also took away the path that is correct for the other case.
For a disk a VMInstance consumes, KubeVirt renders a temporary launcher
pod carrying the VM's own affinity and nodeSelector, so the volume binds
where the VM can actually run; with the annotation always present the CDI
worker becomes the first consumer instead and the volume lands where that
pod happened to be scheduled. On a node-pinned class the VM is then
unschedulable against a node-affinity conflict, and storageClass is
immutable, so the only exit is deleting the disk.

The two cases want opposite defaults and only the operator knows which
one a given disk is. bindImmediately defaults to true, so nothing moves
for existing disks or for anyone on `replicated`, which binds Immediate
either way. Both branches are pinned in tests, including the
existing-DataVolume path, which renders its own annotation block.

Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
Assisted-By: LLM

2026-09-07 16:27:24 +05:00

..

datavolume_test.yaml

feat(vm-disk): let the operator defer binding to the consumer

2026-09-07 16:27:24 +05:00

dv_immutability_test.yaml

docs(vm-disk): record what immediate binding costs on a node-pinned class

2026-09-05 14:51:05 +05:00

dv_source_test.yaml

docs(vm-disk): record what immediate binding costs on a node-pinned class

2026-09-05 14:51:05 +05:00

hook_securitycontext_test.yaml

fix(hooks): run the refreshed alpine/k8s kubectl hooks non-root

2026-06-22 21:26:42 +03:00