So, i got my home lab up and running just fine with the usual suspect apps on Docker:

  • Radarr
  • Sonarr
  • Bazarr
  • QBittorrent
  • NZBGet
  • Jacket
  • Tautulli
  • Overseerr
  • SearxNG
  • PiHole
  • Bitwarden
  • etc.

Now i have deployed an Kubernetes cluster. I’m already running Portainer, Rancher and Traefik on this cluster (MetalLB and Cert-Manager as well).
I want to move most if not all my Docker containers to Kubernetes. I know there is many ways of doing that, but using helm will be the easiest way.

Is any of you doing that? Using Kubernetes for your containers? How are you deploying the containers?

I think that using docker-compose much easier than Kubernetes even with helm and if it (kubernetes) was not de defacto standard for conainer orchestration on the enterprise world (i’m IT professional and learning Kubernetes is kinda a necessity), i would prefeer to use docker-compose with docker-swarm-mode.

  • clintkev251@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    I’m running probably 100 services in Kubernetes in my homelab, most of it is made up of manifests that I’ve written translated over from docker compose files where I used to run the services. I also run some helm charts, but mostly just for more complex sets of services. I commit everything to a private GitHub repository, Flux replicates it to the cluster, and Renovate handles updates. Obviously writing manifests for Kubernetes is way more complex compared to Docker, but that’s kinda the point right, Kubernetes is way more powerful than Docker, so it’s going to come with extra complexity to match

    • fabio_teixei@alien.topOPB
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      Do you mind to explain when to use Helm charts and when to use standard deployments? You said that they are useful for more complex deployments, why is that?