# Kubernetes

333 Hacker News commenters recommended Kubernetes and 288 criticized it, November 2025 to November 2026. It was recommended in 12 of 13 months; owners who said how long report a median of 6 years (22 owners).

**Verdict:** Recommended as a standard, portable way to deploy and scale containers across many machines, backed by a huge ecosystem, though critics call it complex and overkill for small setups.

## Why people recommend it

- Standardized API, transferable knowledge (5 comments): "The reason I like k8s is once you've gone up the learning curve you can apply that knowledge to cloud deployments, on prem, or in this case VPS." ([source](https://news.ycombinator.com/item?id=47739478)) "Having worked with more traditional setups I do think it is often easier to configure config like this in the standardized kubernetes API" ([source](https://news.ycombinator.com/item?id=49056067)) "It is if you stick to standard Kubernetes resources, and it has gotten even easier with better storage class and load balancer support." ([source](https://news.ycombinator.com/item?id=47913974))
- Pays off at scale (5 comments): "it's optimised for a very different scale of operation... But there are plenty of situations in which that scale is required, and it's there that k8s shines." ([source](https://news.ycombinator.com/item?id=45929626)) "At that point it's just one big computer and the abstraction starts to really pay off compared to manually dealing with servers and installation scripts." ([source](https://news.ycombinator.com/item?id=45912916)) "Since k8s is very effective at running a bunch of containers across a few machines, it would appear to be exactly the correct thing to reach for." ([source](https://news.ycombinator.com/item?id=46144768))
- Huge ecosystem, ready-made solutions (4 comments): "Kubernetes built an ecosystem (of contributors and users, but also of companies invested in its success) that none of its competitors could or would." ([source](https://news.ycombinator.com/item?id=48553575)) "Most tasks you would want to do to deploy an application, there's an out of the box solution for k8s that already exists." ([source](https://news.ycombinator.com/item?id=46765671)) "it is operationally not that hard to deal with compared to the things I just mentioned, and has a massive ecosystem" ([source](https://news.ycombinator.com/item?id=48665975))
- Simplifies deployment and config (3 comments): "a Kubernetes deployment is ~50 lines, if I had to build my own scripts with a similar feature set I don't think I would be able to get it down much more than that" ([source](https://news.ycombinator.com/item?id=48933126)) "That was a hell of a lot easier to do with Kubernetes than trying to figure out some giant universe of barely related technologies" ([source](https://news.ycombinator.com/item?id=48034104)) "It's far easier with Kubernetes - just deployment, service secret & ingress config and stuff just works cleanly in namespaces" ([source](https://news.ycombinator.com/item?id=46666988))

## What people warn about

- Overwhelmingly complex, specialized skills (5 comments): "On the application developer side k8s is awesome fo, but the you look inside the box and it melts your face off." ([source](https://news.ycombinator.com/item?id=48553657)) "I hear people say they understand k8s and I can't help but furrow my eyebrows. I don't even pretend to, there are so many insanely complicated edge cases." ([source](https://news.ycombinator.com/item?id=50308132)) "then either your unified IT/DevOps team is responsible for supporting all systems on k8s, or all individual dev teams have to be competent with k8s" ([source](https://news.ycombinator.com/item?id=45912675))
- Hard to set up and maintain (5 comments): "it is not easy to: a) setup and maintain a k8s cluster with all necessary components from at least a dozen different sources" ([source](https://news.ycombinator.com/item?id=47679876)) "There was once a time when we could deploy software without spinning up 3 etcd databases, multiple controller processes constantly running event loops, and a virtual networking layer" ([source](https://news.ycombinator.com/item?id=48549277)) "Anyone who runs a large kubernetes cluster will know that once it's full of state, rebuilding it consistently in a DR scenario is HORRIBLE." ([source](https://news.ycombinator.com/item?id=46676676))
- Verbose YAML boilerplate (4 comments): "K8s yaml looks complex, and can start to feel very boilerplate, but attempts to hide the complexity often just lead to something not-flexible-enough" ([source](https://news.ycombinator.com/item?id=48021863)) "The mental gymnastics required to express oneself in yaml, rather than, say, literally anything else, invariably generates a horror show of extremely verbose boilerplate" ([source](https://news.ycombinator.com/item?id=46396866)) "If your configuration is megabytes of impossible to understand YAML, and is also not portable to other environments, then what's the point?" ([source](https://news.ycombinator.com/item?id=47917524))
- Overkill for small projects (4 comments): "having to manage a bunch of persistent volumes because most of your applications use sqlite is not very practical" ([source](https://news.ycombinator.com/item?id=48934523)) "The problem with Kubernetes is that above-average developers can use it to build small things they can't handle." ([source](https://news.ycombinator.com/item?id=48564457)) "K8s biggest problem is how relatively heavyweight the kublet is, with memory requirements of roughly half a gig." ([source](https://news.ycombinator.com/item?id=46035466))

## Alternatives hackers recommend

- [Docker](https://hackerapproved.com/p/docker.md): 558 recommend
- [Docker Compose](https://hackerapproved.com/p/docker-compose.md): 149 recommend
- [Uncloud](https://hackerapproved.com/p/uncloud.md): 33 recommend
- [Podman Quadlets](https://hackerapproved.com/p/podman-quadlets.md): 30 recommend
- [podman-compose](https://hackerapproved.com/p/podman-compose.md): 8 recommend

## Cite as

Hacker Approved, "Kubernetes", https://hackerapproved.com/p/kubernetes/ (counts from 1,795,640 Hacker News comments, November 2025 to November 2026).
