This message was deleted.
# harvester
a
This message was deleted.
b
Harvester already supports containers? Everything is containers. I'm confused about your statement. Maybe there's certain requirements for specific containers that you have in mind?
While you can access the kubernetes layer underneath with kubectl or other means, in general it's "not supported" meaning you're on your own as there's a million ways you can screw things up that the devs can't plan for or test for things like upgrades.
v
We just want to run a different CNI. Cilium gives us netkit and eBPF support, which should improve performance and integrate with the Cisco ACI Networking. We know how to do this in baremetal kubernetes (Just install Cilium as a Helm Chart and make sure Kubernetes doesn't install kube-proxy so that the cilium proxy is used)... Not sure how possible that is with Harvester. We need VMs and containers, but for the containers, we want Cilium as the CNI.
p
b
Typically it's recommended to use the HarvesterCI to spin up vm based clusters and deploy k3s or rke with cilium (which is supported)
v
I agree with that as a path personally... I see Harvester as a VM supporting product based on containers. If we want to run containers on that same platform (given that Rancher is there), why not... But if we want a more flexible container solution I think that should be Rancher and not Harvester. But I have pressure to push the solution beyond that and want to make sure I am not missing something.
b
afaik, you can't buy harvester support without Rancher.
Harvester licenses are an add on that include entitlements for longhorn and harvester, but they have to have a matching rancher license too.
But licensing has changed like 3 or 4 times since we purchased so who knows.
v
Cilium doesn't replace Rancher. It is more in line with Multus / Bridge CNIs, which I think are the installed CNIs by default... It also replaces the kube-proxy. You can do Multus with Cilium, but I don't know how that works with Havester or what the impact would be...
b
It's how they're baking in the components to the immutable OS that makes it currently not possible.
You can't replace the CNI in harvester currently. They've been talking about adding it for a year, but it's currently not possible. If you want cilium, you'd have to do it with VMs on another downstream cluster.
t
Harvester is not a typical k8s deployment. there are a LOT of trade offs. 1st being it is immutable.
b
afaik, you can't buy harvester support without Rancher.
depends on what exactly you mean but I think you can just get the general SUSE premium support which would give you this https://www.suse.com/services/premium/
but a very different support model (limited cases etc) compared to the normal rancher prime with add ons offering
b
¯\_(ツ)_/¯
t
@victorious-printer-90746 if you need help with licenses I can get you in touch with my old team.
132 Views