• invertedspear@lemm.ee
    link
    fedilink
    arrow-up
    128
    ·
    3 days ago

    To be fair Kubernetes creates copies of the things it drops into the ocean to replace them as fast as they’re lost.

  • AnIndefiniteArticle@sh.itjust.works
    link
    fedilink
    arrow-up
    72
    arrow-down
    1
    ·
    3 days ago

    I’d say that docker compose also has the containers strapped together with holes cut in the walls between them for communication.

    Kubernetes is more the crane that stacks the containers onto passing ships instead of a singular ship itself.

    • h4x0r@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      40
      arrow-down
      1
      ·
      3 days ago

      Seriously! There’s no network, NAT, port forwarding, network isolation - hell, not even any iptables rules in any of these images. This meme makes no fucking sense.

  • Justin@lemmy.jlh.name
    link
    fedilink
    arrow-up
    21
    arrow-down
    4
    ·
    edit-2
    3 days ago

    Kubernetes is more stable than docker compose. Docker compose is fishing for containers after the ship capsized. Frustrating and nothing works out of the box.

    • MangoPenguin@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      21
      arrow-down
      1
      ·
      3 days ago

      Huh? All my docker compose projects work fine ‘out of the box’, the oldest ones have been stable for years now.

    • Gonzako@lemmy.world
      link
      fedilink
      arrow-up
      15
      ·
      3 days ago

      I personally really enjoy interacting with docker compose and I’ve successfully used docker compose to get a 0 downtime setup on my company’s internal web servers by using a reverse proxy

        • setVeryLoud(true);@lemmy.ca
          link
          fedilink
          arrow-up
          1
          ·
          2 days ago

          Is it production-ready?

          I’m thinking of setting it up on an OVH bare metal dedicated server to run various sites and Docker processes, but I don’t want to handle Kubernetes myself.

          • timbuck2themoon@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            3
            ·
            2 days ago

            You always have to manage kubernetes. And talos is nothing but a ready to do k8s os.

            If you don’t want kubernetes I’d suggest something like fedora coreos.

            • setVeryLoud(true);@lemmy.ca
              link
              fedilink
              arrow-up
              1
              ·
              2 days ago

              I’m ok with k8s, I’m just chicken shit because I’ve never had an opportunity to use them in prod.

              How does Talos differ from something like Ubuntu with microk8s?

              • timbuck2themoon@sh.itjust.works
                link
                fedilink
                English
                arrow-up
                1
                ·
                2 days ago

                The only way to interact with it is using talosctl (no ssh, very minimal console, etc.) It is pretty slim and designed only to use k8s. Ubuntu on the other hand is general purpose that can be made to use k8s.

                Basically the idea being that your nodes are also cattle.

                It’s very interesting. I’m debating moving from fedora coreos to it. About to spin up a test cluster whenever I have free time.

          • towerful@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            2 days ago

            I was aware of kubernetes 6 months ago, but had never used it.
            I got a 3 node cluster running in a day, and was learning kubernetes.
            The only issues I’ve had were due to hardware failure causing etcd instability, and misconfigured operators generating terabytes of logs leading to pod eviction.

            I don’t know what would signify it being production ready. It had all the levers and knobs I needed. I haven’t yet needed to run a sysadmin debug container to poke around the host OS.
            It’s also great for learning. If you make a mistake, it’s very easy to wipe and reinstall and get back to where you were.