Fix regional DR kubevirt env config

[akalenyu]

Today volsync is required to start up some of the ramen controllers:

2024-06-02T12:04:48.162Z    ERROR   controller-runtime.source.EventHandler  source/kind.go:68   failed to get informer from cache   {"error": "failed to get API group resources: unable to retrieve the complete list of server APIs: volsync.backube/v1alpha1: the server could not find the requested resource"}

which is an issue because some time ago volsync was disabled (https://github.com/RamenDR/ramen/pull/1213/commits/43266c52d171406ba9417346084594d67fe1efef).

Related - https://github.com/kubernetes-sigs/controller-runtime/issues/2456

[akalenyu]

@nirs Not sure if volsync is an intended requirement or this is a bug

[nirs]

Did you configure ramen after deploying as documented here? https://github.com/RamenDR/ramen/blob/main/docs/user-quick-start.md#deploy-and-configure-the-ramen-operator

If you did, volsync would be disabled and the error you mention would no happen.

See https://github.com/RamenDR/ramen/blob/3d54ae6b006b8137ec87328bc0d01a56d95bdede/ramenctl/ramenctl/config.py#L92

I would like to keep volsync disabled unless we need to test kubevirt with cephfs.

I don’t think it will work for real vms because rsync does not support efficient replication of sparse images.

[akalenyu]

volsync.backub

Yup you're right, once ramenctl config runs the pod will die once and come up with that watch disabled

[akalenyu]

https://github.com/RamenDR/ramen/pull/1433#issuecomment-2143871408