Anyone an opinion about building an HCI like Harvester with Incus?
As there is capi-support this could be a nice niche.
Hi Erkan. I am not familiar with HCI but I did a quick search. How is it different than what Incus and IncusOS already provide? I guess to build out a complete solution you would need to use Incus with a few other technologies. IncusOS either already includes everything or will in the near future.
Are there any pieces missing from your point of view?
1 Like
You’re right. My point is maybe more abount branding make it more public.
Is this what you meant by cluster api?
1 Like
Absolutely.
I’m kinda irritated an “Incus”-based Kubernetes-HCI is not getting more attention. At least in the non US the time is right.
Do you mind doing your best to explain Incus based Kubernetes-HCI? It might help to promote the stack.
Of course sry.
Goal: Manage a lot of (Kubernetes)K8s-Cluster and assume K8s is the way
Offerings:
Harvester: A K8s-Cluster with Longhorn where you can provision additional Clusters on Top of Libvirt
Proxmox: Is not K8s-first but can be used to manage a bunch of K8s-Clusters
Ubuntu MicroCloud: like Proxmox but on top of LXD
Talos/Omni: Omni is not OpenSource
The magic is to use CAPI as @moonpiedumplings referenced to.
I wonder why not to use Incus-cluster as a base to provision k8s-cluster (via CAPI) on top.
Much simpler as Proxmox for sure
1 Like
Are you trying to do kubernetes as a service for people? I wouldn’t really call that “HCI”, to me HCI is more like just Incus, proxmox, XCP, Harvester. More for these small IT shops which like virtualization clusters to make things easy.
Kubernetes as a service is more of a “public cloud” thing.
If you use Rancher (also by Suse), it integrates with Harvester. Then, less privileged users can log in using Ouath2, and create their own Kubernetes clusters, which will auto provision VM nodes from harvester.
There is also Openstack, but that’s it’s own thing, and is a very complex beast.
You could also probably rapidly develop your own, with any of the above, of course.
More an alternative to Harvester and Proxmox.
With the goal to focus on K8s-workloads. As Incus comes as a cluster , able to utilize Ceph and having a capi-provider it is kinda straight forward. Kube-Vip/MetalLB added. I could be a robust setup.
Don’t know why not. It is also not me to start a business. Not my type of game. But providing/starting a setup for people to adopt.