Hello. I'm currently on Harvester 1.0.2 controlled by a Rancher cluster with version 2.6.3. Trying to spin up an RKE2 cluster gives me the following error:

failed to create fleet-default/cluster1 <http://cluster.x-k8s.io/v1alpha4|cluster.x-k8s.io/v1alpha4>, Kind=Cluster for rke-cluster fleet-default/cluster1: Internal error occurred: failed calling webhook "<http://default.cluster.cluster.x-k8s.io|default.cluster.cluster.x-k8s.io>": failed to call webhook: the server could not find the requested resource, failed to create fleet-default/cluster1-bootstrap1 <http://cluster.x-k8s.io/v1alpha4|cluster.x-k8s.io/v1alpha4>, Kind=MachineDeployment for rke-cluster fleet-default/cluster1: Internal error occurred: failed calling webhook "<http://default.machinedeployment.cluster.x-k8s.io|default.machinedeployment.cluster.x-k8s.io>": failed to call webhook: the server could not find the requested resource

I've been trying to trace the error but I'm having some difficulties finding the correct related objects in the two kubernetes clusters. What I suspect might be the issue is that rancher attempts to create a machinedeployment on the harvester cluster, which is in the api namespace

<http://cluster.x-k8s.io/v1beta1|cluster.x-k8s.io/v1beta1>

while rancher expects it to be in the api namespace

<http://cluster.x-k8s.io/v1alpha4|cluster.x-k8s.io/v1alpha4>

Before I go through the hoops of upgrading rancher I figured I'd check here if this is a known issue. If so, are there plans to support some amount of backwards compatibility from different rancher versions to harvester and vice versa?

It will be great if you could file an issue in harvester github

i suspect error is likely on the rancher end.. may be a validatingwebhook is not ready