This message was deleted.
# harvester
a
This message was deleted.
l
I had this exact thought but I don't think its a good idea anymore
They recently published a terraform provider and now I think the best solution for this is to push people towards the api via the terraform provider and produce a rancher-on-harvester terraform module that accomplishes the same thing. That way the feature is customer driven instead of ui/vendor driven
b
b
Thank you @bored-painting-68221
@loud-motorcycle-81 well, I get that it's possible to provision a VM https://registry.terraform.io/providers/harvester/harvester/latest/docs/resources/virtualmachine but it would be an overkill, and I don't really need rancher up and running 24x7... so, I'd rather wrap it up in a HPA/VPA goldilocks, as well.
l
yeah that's fair. But if you are planning to host a k8s cluster on a harvester cluster (recommended I think), rather than deploy directly to the harvester cluster itself, you'd already have another cluster you could deploy rancher in.
I suppose, if you're purely coordinating vms that are not for the purpose of a k8s cluster then having rancher deployed on the harvester hits on the points you made
b
Well... it doesn't work for some reason I'm getting 401's
mb wrong passwd
Nah... all good