Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

petekeen.net

Post reply on HN
Print view View original

41–50 of 66 posts

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#41

Post by anymouse123456 »

ocd wrote: post #3

I still don't know really what Kubernetes is for or why so many people outside specific environments are using it, but it's cool that you're using Ruby.

Kubernetes is an attempt to solve the problems that come from deploying, Microservices™ across a gigantic enterprise with hundreds (or thousands) of contributors.

If you are one person and just need to expose a handful of macro-services, Kubernetes is almost entirely made of waste in terms of complexity, abstraction, indirection and resource consumption.

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#42

Post by lachiflippi »

vachina wrote: post #33
MisterKent wrote: post #7

Lot of kubernetes hate here, which is surprising. I run a little 3 node cluster and besides the hardware issues I had (long story), it has been rock solid and dead easy to setup. Talos + longhorn + fluxcd (optional), is super nice. And everything beyond that is additive and just works within the ecosystem. If anything, it helped keep my stuff alive during all the hardware issues a lot longer. I think like 5-6 years a…

> Talos + longhorn + fluxcd Are you running a startup at home.

That's, in my opinion, a pretty vanilla starter stack. Could probably argue that you don't need replicated storage, and that ArgoCD is nicer to look at, but Talos in particular simplifies a lot of the deployment because there's not much of an OS to configure or keep updated.

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#43

Post by felooboolooomba »

MisterKent wrote: post #7

Lot of kubernetes hate here, which is surprising. I run a little 3 node cluster and besides the hardware issues I had (long story), it has been rock solid and dead easy to setup. Talos + longhorn + fluxcd (optional), is super nice. And everything beyond that is additive and just works within the ecosystem. If anything, it helped keep my stuff alive during all the hardware issues a lot longer. I think like 5-6 years a…

> Lot of kubernetes hate here, which is surprising

It's easier when you think of it using cats. A person wants a cat. They want a big one to deal with their rodent problem. They've heard that tigers are really big cats and extremely efficient in dealing with unwanted biomass around them.

Said person gets a tiger. They get an impromptu expedition to hell and barely make it back. Person hates cats, buys a poodle and advocates for mouse traps.

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#44

Post by astralkraft »

catdog wrote: post #40
astralkraft wrote: post #34

Earlier quoted context omitted.

Proxmox is merely Debian with some fancy curtains. I'm sort of fascinated by this social belief it is something more than that. Although I agree with your sentiment, I'd rather be on XCP-ng or IncusOS as the foundation for containers. I don't believe sacrificing immutability in the host is an improvement over k8s for stability and maintenance.

> Proxmox is merely Debian with some fancy curtains. It's part of the appeal that it is mostly just Debian under the hood. If I want to run containers I would also not see it as the best choice but it really shines in managing qemu VMs.

Proxmox upgrades make K8s appealing, and that's not easily done.

I've been on Incus with my homelab for a few months now, and couldn't be happier. Maybe I should make a post about it, but I don't have much to report. My biggest maintenance outage was forgetting to set WakeOnPower in the BIOS.

Edit: And yes, all I want to do is run containers. Nothing fancy, Nginx Proxy Manager suffices for networking, and Linstor/DRBD handles disk. I wanted to remove hyperscaling complexity, but keep immutability, and so far, life is good.

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#45

Post by maxrecursion »

felooboolooomba wrote: post #43
MisterKent wrote: post #7

Lot of kubernetes hate here, which is surprising. I run a little 3 node cluster and besides the hardware issues I had (long story), it has been rock solid and dead easy to setup. Talos + longhorn + fluxcd (optional), is super nice. And everything beyond that is additive and just works within the ecosystem. If anything, it helped keep my stuff alive during all the hardware issues a lot longer. I think like 5-6 years a…

> Lot of kubernetes hate here, which is surprising It's easier when you think of it using cats. A person wants a cat. They want a big one to deal with their rodent problem. They've heard that tigers are really big cats and extremely efficient in dealing with unwanted biomass around them. Said person gets a tiger. They get an impromptu expedition to hell and barely make it back. Person hates cats, buys a poodle and ad…

That's a very accurate and elegant analogy.

Kubernetes was designed for large organizations with massive applications that are usually micro services. It allowed the applications to be load balanced and easily updated with no downtime. Also, these organizations paid top dollar to highly technical and competent employees.

Now, all organizations feel like they need kubernetes because it's the next logical step in the never ending IT progression. So, they force all their apps to be containerized and run on an multi-tenant cluster.

However, these apps worked just fine on a server, and now the devs have to refactor them and get them to work on kubernetes. All the System Admins and Engineers also need to learn kubernetes. But most of these people don't want to constantly learn and use kubernetes, so no one ever really knows how it all works.

This inevitably led to companies whose sole purpose is to help places get off of kubernetes because it is too hard to maintain. I've seen it play out at several organizations.

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#46

Post by [deleted] »

dspillett wrote: post #36
MisterKent wrote: post #7

Lot of kubernetes hate here, which is surprising. I run a little 3 node cluster and besides the hardware issues I had (long story), it has been rock solid and dead easy to setup. Talos + longhorn + fluxcd (optional), is super nice. And everything beyond that is additive and just works within the ecosystem. If anything, it helped keep my stuff alive during all the hardware issues a lot longer. I think like 5-6 years a…

> an LLM can probably That would not match their reason for preferring to move off k8: > I built a system that I didn't actually know how to maintain without the time or energy necessary to dig myself out of trouble. If you want a system that you can understand all at once in your own head then making it with your own head is a better way to go IMO, for a small system at least.

[deleted]

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#47

Post by PunchyHamster »

MisterKent wrote: post #7

Lot of kubernetes hate here, which is surprising. I run a little 3 node cluster and besides the hardware issues I had (long story), it has been rock solid and dead easy to setup. Talos + longhorn + fluxcd (optional), is super nice. And everything beyond that is additive and just works within the ecosystem. If anything, it helped keep my stuff alive during all the hardware issues a lot longer. I think like 5-6 years a…

It's all nice till something breaks and you need to debug something, and when it does the less layers you have the easier it becomes

> All the enterprisey stuff makes it feel a lot more complex than it really is.

It is insanely complex under the hood. We just got to level when for most cases the tools available work just fine.

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#48

Post by PunchyHamster »

dewey wrote: post #10
MisterKent wrote: post #7

Lot of kubernetes hate here, which is surprising. I run a little 3 node cluster and besides the hardware issues I had (long story), it has been rock solid and dead easy to setup. Talos + longhorn + fluxcd (optional), is super nice. And everything beyond that is additive and just works within the ecosystem. If anything, it helped keep my stuff alive during all the hardware issues a lot longer. I think like 5-6 years a…

When you are only used to the Kubernetes at work I can understand how people dislike it. If you set it up yourself and start with minimal feature and not lots of annotations the config files become very simple and not more complicated than a docker compose file. It quickly realized that after just using the managed Kubernetes from Digital Ocean and deploying a side project there.

Oh running stuff on k8s is great, but running k8s itself is just adding a lot of code to your stack and might be not so trivial to debug when something goes wrong.

Then again tools to deploy it went a long way

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#49

Post by dewey »

PunchyHamster wrote: post #48
dewey wrote: post #10

Earlier quoted context omitted.

When you are only used to the Kubernetes at work I can understand how people dislike it. If you set it up yourself and start with minimal feature and not lots of annotations the config files become very simple and not more complicated than a docker compose file. It quickly realized that after just using the managed Kubernetes from Digital Ocean and deploying a side project there.

Oh running stuff on k8s is great, but running k8s itself is just adding a lot of code to your stack and might be not so trivial to debug when something goes wrong. Then again tools to deploy it went a long way

Agreed, personally I'd only do it through a hosted provider or maybe consider https://k3s.io for a bit simpler setup. I'd also only do it if Kubernetes is something I'm already familiar with.

Re: Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes

#50

Post by astralkraft »

SMFloris wrote: post #5

IMO, kubernetes is overkill for a small non-homogeneous home cluster. What I use and really recommend is using systemd +/- docker. It just becomes so darn simple. Do not go the compose route (that route is filled with sadness of the incomplete stacks because db container failed silently kind) - instead aim to decompose the compose files and write a separate systemd service file for each of them, you can then assign l…

NixOS, IncusOS, FCOS Atomic. Completely agree. Immutable host. This is the way
Post reply on HN