This message was deleted.
# harvester
a
This message was deleted.
t
Harvester is a bare metal OS. Install it on the node itself. There are 2 options for Rancher. A. a vm with rke2, or k2s. B. Rancher running in a vcluster directly on Harvester : https://docs.harvesterhci.io/v1.5/advanced/addons/rancher-vcluster I made a video on all of this :

https://youtu.be/pHttkWS0pPo

I would play and test both ways. It really comes down to how you want to manage things.
If you are going to be managing other clusters. I would decouple Rancher from harvester by running outside. So not in a VM or on cluster. You can run Rancher in a VM in the cloud to manage harvester on prem. Here is a demo :

https://www.youtube.com/watch?v=9y37tuMBSUg

g
Looks like I had a typo in my original post because my actual question where I should be installing Rancher onto my harvester cluster. Oops. So there's no real support/it's not recommended to deploy rancher as a workload directly onto the harvester underlying RKE2 cluster, using the manual helm install in the rancher docs? It should always be in a whole vcluster/VM, and thus nested kubernetes? And the other clusters I eventually run are a few offsite single node servers that currently have NixOS on them. If I like what I achieve with this cluster I'd fold them under rancher and spin up harvester on them; They're 99% just to have backups of data and don't do a whole lot regardless, and it's not an issue for me if Rancher goes down on my home cluster. Thanks for the vids for sure. Will definitely take a watch and think I've come across them before in my searches.
👍 1