mirror of
https://github.com/cozystack/cozystack.git
synced 2026-11-09 14:02:56 +09:00
The right value of --enable-vmi-hotplug-fallback is decided by the KubeVirt CR in packages/system/kubevirt, not by the tenant: it must stay true while that CR enables HotplugVolumes and turn false in the same change that drops the gate. A note beside the gate in the CR points at the controller Deployment, and a helm-unittest pins the flag off the rendered args. The chart relies on the driver default instead of rendering =true. The driver image is stamped only at release preparation, so between releases the chart on main runs the previous release's binary, which does not know the flag, and Go's flag package exits on an unknown one: rendering the default would crash-loop the controller for no effect. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <f@lex.la>
How to test packages local
cd packages/core/installer
make image-cozystack REGISTRY=YOUR_CUSTOM_REGISTRY
make apply
kubectl delete po -l app=source-controller -n cozy-fluxcd