https://rancher.com/ logo
#harvester
Title
# harvester
a

adamant-kite-43734

02/05/2023, 6:02 PM
This message was deleted.
g

great-bear-19718

02/05/2023, 9:54 PM
not sure i understand the question. the rancher embedded with the harvester installation should not be leverage for general purpose workloads. It only exists to perform some api aggregation work for harvester and also troubleshoot if needed
we recommend rancher be deployed in a VM, because rancher expects ownership of certain namespaces / objects which will conflict with the embedded rancher, which is packaged with Rancher
g

gentle-dentist-69634

02/06/2023, 11:20 AM
Yes, you understood it correctly. I know about the recommendation. It would be nice to have Rancher without additional VMs, that would make vGPU management for VMs (through vGPU) and GPU-accelerated containers much easier. I‘ve enabled the „developer“ feature and the embedded Rancher is completely fine for me. Thank you for your response. I hope the „embedded Rancher“ feature will not disappear at some point.
3 Views