• Lodra
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    3
    ·
    12 hours ago

    Honestly, k8s is super easy and very lightweight to run locally if you know the rights tools. There are a few good options but I prefer k3d. I can install Docker/k3d and also build a local cluster running in maybe 2 minutes. It’s excellent for local dev. Even good for production in some niche scenarios

    • cley_faye@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      4 hours ago

      I don’t like the approach of piling more things on top of even more things to achieve the same goal as the base, frankly speaking. A “local” kubernetes cluster serve no purpose other than incredible complexity for little to no gain over a mere docker-compose. And a small cluster would work equally well with docker swarm.

      A service, even made of multiple parts, should always be described that way. It’s easy to move “up” the stack of complexity, if you so desire. Having “have a k8s cluster with helm” working as the base requirement sounds insane to me.

    • Metju@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      4 hours ago

      Seconding k3d (and, by extension, k3s). If you’re in a market for sth suitable for more upstream-compliant clustering solution (k3s uses SQLite instead of etcd, iirc), RKE2 is also a great choice