Many of the posts I read here are about Docker. Is anybody using Kubernetes to manage their self hosted stuff? For those who’ve tried it and went back to Docker, why?

I’m doing my 3rd rebuild of a K8s cluster after learning things that I’ve done wrong and wanted to start fresh, but when enhancing my Docker setup and deciding between K8s and Docker Swarm, I decided on K8s for the learning opportunities and how it could help me at work.

What’s your story?

  • wsis@feddit.cl
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 years ago

    Kubernetes is useful if you have gone full cattle over pets. And that is very uncommon in home setups. If you only own one or two small machines you cannot destroy infra easily in a “cattle” way, and the bloatware that comes with Kubernetes doesn’t help you neither.

    In homelabs and home servers the pros of Kubernetes are not very useful: high availability, auto-scaling, gitops integrations, etc: Why would you need autoscaling and HA for a SFTP used only by you? Instead you write a docker-compose.yml and call it a day.

    • jsnfwlr@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 years ago

      The one exception to this is if you’re using your homelab to learn kubernetes.

      That was the only time I used K8s and k3s on my homelab.

      And for anything that I do want to set up in a HA/cattle kind of way, I use Docker Swarm, as it feels like a more comfortable extension of docker compose.

  • Oliver Lowe@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 years ago

    Here’s a slightly different story: I run OpenBSD on 2 bare-metal machines in 2 different physical locations. I used k8s at work for a bit until I steered my career more towards programming. Having k8s knowledge handy doesn’t really help me so much now.

    On OpenBSD there is no Kubernetes. Because I’ve got just two hosts, I’ve managed them with plain SSH and the default init system for 5+ years without any problems.

  • AntBas@eslemmy.es
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 years ago

    I was looking into converting my docker services into a cluster to get high availability and to learn it for work, but while investigating it, I read that kubernetes is actually meant for scalability and just a single service per cluster.

    Also read that docker swarm is actually what is recommended for my homelab use case. So I’m right now on my way to convert everything to docker stacks. What do you think?

    • Lmaydev@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      ·
      3 years ago

      I’m not sure what you mean by that.

      It provides high availability if you have multiple nodes and pods.

      Also what do you mean by single service per cluster? Because that’s not the idea at all.

      • AntBas@eslemmy.es
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 years ago

        Of course high availability always requires multiple nodes.

        Its just that while choosing how to set up my cluster I looked up several options (proxmox, swarm, kubernetes…) and I noticed that kubernetes is generally meant for bigger deployments.

        I only need a single replica for each of my containers and they can all run on a single node, so kubernetes is overkill just to get high availability For my use case

  • orizuru@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    3 years ago

    Seems a bit overkill for a personal use selfhosting set-up.

    Personally, I don’t need anything that requires multiple replicas and loadbalencers.

    Do people who have homelabs actually need them? Or is it just for learning?

    • egonallanon@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 years ago

      I find mine useful as both a learning process and as a thing need. I don’t like using cloud services where possible so I can set things up to replace having to rely on those such as next loud for storage, plex and some *arr servers for media etc. And I think once you put the hardware and power costs vs what I’d pay for all the subs (particularly cloud storage costs) it comes out cheaper at least with hardware I’m using.

    • kelvie@lemmy.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 years ago

      A lot of people thought this was the case for VMs and docker as well, and now it seems to be the norm.

      • orizuru@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 years ago

        A lot of people thought this was the case for VMs and docker as well, and now it seems to be the norm.

        Yes, but docker does provide features that are useful at the level of a hobbyist self-hosting a few services for personal use (e.g. reproducibility). I like using docker and ansible to set up my systems, as I can painlessly reproduce everything or migrate to a different VPS in a few minutes.

        But kubernetes seems overkill. None of my services have enough traffic to justify replicas, I’m the only user.

        Besides learning (which is a valid reason), I don’t see why one would bother setting it up at home. Unless there’s a very specific use-case I’m missing.