https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# harvester
a
This message was deleted.
b
Do you mean for Rancher to provision a harvester cluster but not do the LB from service creation? I'm pretty sure you can do that by choosing the Default - RKE2 Embedded option at provisioning instead of using the Harvester Cloud Provider
Kube-vip is what deploys with the harvester provider and does the LB > Service thing.
s
We are using Cilium L2 and thus can skip having thr cloud provider doing it
b
Yeah I needed to run and ship my own kube-vip and needed to skip that part and changing that option allows me to do it so I can have a vip for the cluster.
While it would be nice to have an option within the cloud provider to do it, you can get around with by just not using it.
s
.what does the embedded option do under the hood?
b
Just standard options afaik.
s
it uses the cloud provider?
b
It doesn't, which is the point. That's not to say it doesn't use Harvester, It's just not using harvester cloud provider helm/charts/values inside the downstream cluster.
It still provisions VMs/pools in harvester though.
s
uh how can you do csi without it? :)
b
With the embedded RKE one. 🙂
s
ah so you sont use harvester for csi?
b
It just might take a little extra config to get the standard RKE bits to work with harvester stuff.
s
that pdf looks all rke to dell stuff?
b
yeah it's just pointing out the built in RKE stuff for Dell
Feel free to google fu some better results. 🙂
s
I can't see however how the CSI for rke2 would be diff on harvester then for generic usage of the cloud-provider ? 🤔
Open in Slack
PreviousNext
Powered by