This message was deleted.

same thoughts and problems I have been running into. I understand SUSE focusing on harvester JUST being about HCI even though they use rancher under the covers along with longhorn and the requirement to install Rancher outside of the harvester cluster so the rancher manager itself will not be affected by any disk or network pressure issues (which I have run into) but it does seem like a mess of slimy noodles, doesn't it? I recognize what they are trying to do and it's admirable but it's. 'just not quite there yet'

im going backwards to Proxmox VE. It was stable and worked well. Since using harvester for 6-8 months, Ive had nothing but issues with crashing VM’s, VM’s constantly pausing, Upgrade not working 5 times in a row, then saying my cluster is up to date despite the hosts all still being on the previous version. Longhorn is an absolute DOG of a storage platform (even with full SSD/NVME disks). Unless you run 10G networking (or much more), dont even bother with Harvester, its too immature. I too hope this platform takes off, as I really want to use it at work, but for home-users its a nightmare. Definitely shouldnt be in stable-production-release.

i found out about harvester only a few hours after I renewed my vmug advanced for this year and I was hoping it would be something I could use at home for free that works like the kubernetes stuff I already use and like

It is usual to run a Rancher VM on Harvester to manage the Harvester cluster, and other clusters, although that is not something I have done.

@flat-evening-58664 same boat I was/am in. I'm a VCP with VMUG as well and have been using an little Intel NUC for years as a nested VMware lab and thought I'd give this harvester thing a shot. Super interested and the bits combined make sense just not mature enough yet in both industry adoption (plugins, ecosystem, etc.) as well as being polished. It's supposed to be a black box but unfortunately I have had to resort to pulling back the covers a bit too often to find things that /should/ be part of the UI. For example, as we speak I am troubleshooting a VM that is stuck stopping in the UI and have had to resort to a kubectl describe to find out what is going on with it. Just not primetime IMHO

@sticky-summer-13450 Is it really usual to run the controlling Rancher on the same Harvester it is managing? I doubt it... at least for production. And I also didn't find a recommendation for that. My advice: run Rancher outside Harvester... on a dedicated rke2 cluster, not a single VM. My 2 cents.