• sudneo@lemm.ee
    link
    fedilink
    English
    arrow-up
    8
    ·
    3 months ago

    Yeah, but you don’t need anything besides the runtime with kubernetes. Podman is completely unnecessary since kubelet does the container orchestration based on Kubernetes control plane. Running podman is like running docker, unnecessary attack surface for an API that is not used by anybody (in Kubernetes).

    I run k0s at home, FWIW, tried k3s too :)

    • 1984
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      Yeah I know.

      Interesting that you run k0s, hadn’t heard about it. Would you mind giving a quick review and compare it to k3s, pros and cons?

      • sudneo@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 months ago

        I can’t really make an exhaustive comparison. I think k3s was a little too opinionated for my taste, with lots of rancher logic in it (paths, ingress, etc.). K0s was a little more “bare”, and I had some trouble in the past with k3s with upgrading (encountered some error), while with k0s so far (about 2 years) I never had issues. k0s also has some ansible role that eases operations, I don’t know if now also k3s does. Either way, they are quite similar overall so if one is working for you, rest assured you are not missing out.

        • 1984
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          I watched some video on YouTube also where k0s seems to be slightly better at throughput, which can matter if your cluster is under heavy load a lot. But yeah, seems to be smaller differences and mostly about taste.