Hopefully just a yes/no question: Is the rancher ...
# harvester
r
Hopefully just a yes/no question: Is the rancher instance spun up within a harvester cluster designed to be interfaced with? The alternative would be to spin up a rancher cluster within the harvester cluster using VMs and manage the harvester cluster (and it's built-in rancher cluster) from inside the new, nested rancher cluster.
n
yes you could run the rancher instance from a VM created inside Harvester cluster and you can manage your Harvester cluster from the rancher by importing it to your rancher cluster.
r
Right - I know I could do that, but is that the intended design? Like, for example, what is stopping me from creating a load balancer or exposing ingress to the built-in rancher deployment that comes with harvester?
In that example, a fresh harvester cluster being managed by rancher would have a single rancher deployment. You wouldn't then have to also create a second rancher environment to manage the first
And this could be my own ignorance talking - I'm making an assumption that the rancher/cattle-system namespaces and containers within a harvester cluster are the same as what you would deploy via "helm install rancher"
They very well could be different and meant for different purposes but just happen to be named the same because its the same underlying code
n
I am not sure about "helm install rancher".Adding some experts in that area @great-bear-19718 @red-king-19196
g
we do not recommend using the embedded rancher since it has a few features disabled and its upgrade cycle among other things is managed by harvester itself
💚 1
if you need a rancher to manage harvester our recommendation is to run it in vm or via the vcluster addon(which is currently experimental)
👍 2