Comment by loloquwowndueo
7 months ago
Not really, Kubernetes does a lot of different things that are out of scope for incus or lxd or docker compose for that matter or any hypervisor or …
7 months ago
Not really, Kubernetes does a lot of different things that are out of scope for incus or lxd or docker compose for that matter or any hypervisor or …
like what? I'd love to hear some examples of things Kubernetes does that incus doesn't at this point
Service discovery?
I'm sure you could probably manually hook up Incus to something like Consul, but it would be more effort than it's worth.
Hmmn... I think it really depends on what you call "service discovery", but I'd note that k8s doesn't give you something as complicated as Consul either -- by default, you get DNS & IP networking for service discovery, which Incus also supports.
If you mean service discovery as in being able to use the k8s API (ex. to find service manually) from inside your application, then incus allows for that too..
Maybe the key difference you're pointing at here is that Incus does not give you one huge network (where by default everything is routable), so you have to set up your own bridge networks:
https://linuxcontainers.org/incus/docs/main/explanation/netw...
https://linuxcontainers.org/incus/docs/main/reference/networ...
I could definitely agree here that Incus is more unencumbered in this respect
3 replies →
One is for cluster orchestration the other is a single machine container/vm runtime.
https://linuxcontainers.org/incus/docs/main/explanation/clus...
https://linuxcontainers.org/incus/docs/main/explanation/clus...
You may have a point there that k8s is not meant for single machines but that’s not a hard rule, more like a “why would you want to” you can absolutely run single node Kubernetes.
Also strictly speaking incus is not a container nor vm runtime, it’s an orchestrator of those things.