This message was deleted.

not really, most cloud providers don’t do the right thing if they find nodes in the cluster with an unknown or unhandled provider id

understood, I'm actually more looking for the On-Prem and Bare metal Cases. i.e. where there might be a Harvester hosting VMs and further Bare Metal nodes. And the cluster might be build from VM Master, and VM OR BM Worker Pools

yeah, kubernetes doesn’t handle that sort of hybrid provider setup well.

Hello Holger, Addressing your requirement of creating a cluster using On-Prem and Bare Metal, we would recommend you to consider RKE2 as your kubernetes engine, as rke2 can be installed on vps, bare metal, aws, google cloud, or on other cloud providers https://www.suse.com/suse-rke2/support-matrix/all-supported-versions/rke2-v1-27/. We have had success with setting-up kubernetes with vps hosting, dedicated server hosting using rke2 with this article https://ranchermanager.docs.rancher.com/how-to-guides/new-user-guides/kubernetes-cluster-setup/rke2-for-rancher, and the metallb https://metallb.universe.tf/ load balancer and other plugins we needed include cert-manager, the rancher nginx-ingress to implement the same. We setup our cluster about a year back using vps, server at contabo using rke2 using the above article, we setup the kubernetes cluster with the public ip address of the server provided by contabo, and used the metallb load balancer to use the vps network ports, with the nginx-ingress for service discovery, and cert-manager is required for the lets encrypt certificates. Using the above method, rke2 can be deployed on vps, vds or dedicated server to be a node, and you can register the nodes on the rancher server as mentioned in the rancher document listed above. Hope this helps! Thanks and Best Regards, Santosh