• cley_faye@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    10 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.

    • Lodra@programming.dev
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      6 hours ago

      Yea I’m not a fan of helm either. In fact, I avoid charts when possible. But kustomize is great.

      I feel the same way about docker compose. If it wasn’t already obvious, I’m biased in favor of k8s. I like and prefer that interface. But that’s just preference. If you like docker compose, great!

      There’s one point where I do disagree however. There are scenarios where a local k8s cluster has a good and clear purpose. If your production environment runs on k8s, then it’s best to mirror that locally as much as possible. In fact, there are many apps that even require a k8s api to run. Plus, being able to destroy and rebuild your entire k8s cluster in 30s is wonderful for local testing.

      Edit: typos

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

        I won’t argue with the ups and downs of each technos, but I recently looked into docker swarms and it was all I expected kubernetes to be, without the hassle. And I could also get a full cluster with services restored from scratch in 30s. But I am obviously biased towards it, too :)