Is your feature request related to a problem? Please describe
When deploying a cluster from the Rancher UI (version 2.13.2), deployment of the nodes initially fails because the storage does not support linked clones.
To work around this is I patched the rke-machine-config:
kubectl patch pveconfigs.rke-machine-config.cattle.io -n fleet-default nc-cluster-pool1-jxr4c --type=merge -p '{"fullClone": true}'
Describe the solution you'd like
The UI needs a checkbox to enable/disable fullClone.
Describe alternatives you've considered
Alternatively set fullClone by default to true, in this instance regardless of the storage backend it will always deploy.
Is your feature request related to a problem? Please describe
When deploying a cluster from the Rancher UI (version 2.13.2), deployment of the nodes initially fails because the storage does not support linked clones.
To work around this is I patched the rke-machine-config:
kubectl patch pveconfigs.rke-machine-config.cattle.io -n fleet-default nc-cluster-pool1-jxr4c --type=merge -p '{"fullClone": true}'Describe the solution you'd like
The UI needs a checkbox to enable/disable fullClone.
Describe alternatives you've considered
Alternatively set fullClone by default to true, in this instance regardless of the storage backend it will always deploy.