Hi. more like a question:
Is there a specific reason this is hard-coded to RunOnce for the kubevirt probvider?
RunStrategy: &runStrategyOnce,
There's other strategies available: https://pkg.go.dev/kubevirt.io/api/core/v1#VirtualMachineRunStrategy
I guess it makes sense as default, but consider this: If a kubevirt host dives (restarts) all the kubermatic VMIs do not restart (unless you live-migrate to another host, if there's another available). Would it be possible to make this field configurable via machineTemplate? The default can still be RunOnce, but eg. in our use-case we would prefer to use RerunOnFailure
Hi. more like a question:
Is there a specific reason this is hard-coded to RunOnce for the kubevirt probvider?
RunStrategy: &runStrategyOnce,
There's other strategies available: https://pkg.go.dev/kubevirt.io/api/core/v1#VirtualMachineRunStrategy
I guess it makes sense as default, but consider this: If a kubevirt host dives (restarts) all the kubermatic VMIs do not restart (unless you live-migrate to another host, if there's another available). Would it be possible to make this field configurable via machineTemplate? The default can still be RunOnce, but eg. in our use-case we would prefer to use
RerunOnFailure