Comment by hardwaresofton

7 months ago

like what? I'd love to hear some examples of things Kubernetes does that incus doesn't at this point

7 comments

hardwaresofton

Reply
ChocolateGod  7 months ago

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.

  • hardwaresofton  7 months ago

    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

    • ChocolateGod  7 months ago

      For the most part, DNS service discovery is good for a lot of use cases where you just want one service to find another service without needing to hardcode IPs/ports.

    • mdaniel  7 months ago

      > by default, you get DNS & IP networking for service discovery, which Incus also supports.

      Supports, as in "good luck with your perl scripts" or, as Kubernetes does, automatically updates dns with the A record(s) and SRV records of the constituent hosts? Because I didn't see anything in the docs about DNS support and I don't know systemd well enough to know what problem this is solving <https://linuxcontainers.org/incus/docs/main/howto/network_br...>

      1 reply →

lifty  7 months ago

One is for cluster orchestration the other is a single machine container/vm runtime.