Files
cozystack/packages
Aleksei Sviridkin 8dcf950842 fix(kubernetes-nodes)!: resolve an empty class to CDI's virtualization default
CDI binds a kubevirt-content DataVolume that names no class on the
class annotated storageclass.kubevirt.io/is-default-virt-class before it
falls back to the Kubernetes default. The worker image guard resolved an
empty class to the Kubernetes default only, so on a cluster carrying
both it compared the golden against a class the golden was not on and
refused a pool that matched it.

CDI's fallback reads only the GA default annotation, so the beta one no
longer ties with it: a class carrying only the beta annotation is picked
only when no class carries the GA one. CDI then creates no claim at
all for a DataVolume naming neither a class nor access modes, so such a
pool gets that class only because the chart writes it onto the worker
disk.

The resolution also refuses a pool that rendered before: one with an
empty class that has not cloned a disk yet, whose golden is on the
Kubernetes default, on a cluster where another class carries the
virtualization default. Its storageClass is immutable, so it has to
point osImage.builtin at a catalog entry on the virtualization default
or switch to osImage.factory. A pool that already cloned reads its
class back from its own disk's claim and keeps rendering.

Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <f@lex.la>
2026-11-17 11:20:19 +03:00
..