Skip to content

Developer tools · container orchestrator

Kubernetes

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.

Summarized from 832 comments.

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.

recommend
333
criticize
288
months recommended
12 of 13
median owned, 22 owners said
6 years

Why people love it

  • Standardized API, transferable knowledge · 5

    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.

    Apr 2026 · comment

    Having worked with more traditional setups I do think it is often easier to configure config like this in the standardized kubernetes API

    Jul 2026 · comment

    It is if you stick to standard Kubernetes resources, and it has gotten even easier with better storage class and load balancer support.

    Apr 2026 · comment
  • Pays off at scale · 5

    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.

    Nov 2025 · comment

    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.

    Nov 2025 · comment

    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.

    Dec 2025 · comment
  • Huge ecosystem, ready-made solutions · 4

    Kubernetes built an ecosystem (of contributors and users, but also of companies invested in its success) that none of its competitors could or would.

    Jun 2026 · comment

    Most tasks you would want to do to deploy an application, there's an out of the box solution for k8s that already exists.

    Jan 2026 · comment

    it is operationally not that hard to deal with compared to the things I just mentioned, and has a massive ecosystem

    Jun 2026 · comment
  • Simplifies deployment and config · 3

    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

    Jul 2026 · comment

    That was a hell of a lot easier to do with Kubernetes than trying to figure out some giant universe of barely related technologies

    May 2026 · comment

    It's far easier with Kubernetes - just deployment, service secret & ingress config and stuff just works cleanly in namespaces

    Jan 2026 · comment

What people warn about

  • Overwhelmingly complex, specialized skills · 5

    On the application developer side k8s is awesome fo, but the you look inside the box and it melts your face off.

    Jun 2026 · comment

    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.

    Oct 2026 · comment

    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

    Nov 2025 · comment
  • Hard to set up and maintain · 5

    it is not easy to: a) setup and maintain a k8s cluster with all necessary components from at least a dozen different sources

    Apr 2026 · comment

    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

    Jun 2026 · comment

    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.

    Jan 2026 · comment
  • Verbose YAML boilerplate · 4

    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

    May 2026 · comment

    The mental gymnastics required to express oneself in yaml, rather than, say, literally anything else, invariably generates a horror show of extremely verbose boilerplate

    Dec 2025 · comment

    If your configuration is megabytes of impossible to understand YAML, and is also not portable to other environments, then what's the point?

    Apr 2026 · comment
  • Overkill for small projects · 4

    having to manage a bunch of persistent volumes because most of your applications use sqlite is not very practical

    Jul 2026 · comment

    The problem with Kubernetes is that above-average developers can use it to build small things they can't handle.

    Jun 2026 · comment

    K8s biggest problem is how relatively heavyweight the kublet is, with memory requirements of roughly half a gig.

    Nov 2025 · comment

What hackers pick instead

Every quote

The 40 most detailed of 832 comments. Each links to the original.

  1. 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

    Recommends · Jul 2026 · in “Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes”

  2. 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.

    Recommends · Nov 2025 · in “Kubernetes Ingress Nginx is retiring”

  3. 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.

    Recommends · Nov 2025 · in “Helm 4.0”

  4. Kubernetes built an ecosystem (of contributors and users, but also of companies invested in its success) that none of its competitors could or would.

    Recommends · Jun 2026 · in “What job interviews taught me about Kubernetes”

  5. 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

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  6. 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.

    Recommends · Dec 2025 · in “Uncloud - Tool for deploying containerised apps across servers without k8s”

  7. 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.

    Recommends · Apr 2026 · in “I run multiple $10K MRR companies on a $20/month tech stack”

  8. Having worked with more traditional setups I do think it is often easier to configure config like this in the standardized kubernetes API

    Recommends · Jul 2026 · in “Open-weight AI is having its Kubernetes moment. Let's not ruin it”

  9. It is if you stick to standard Kubernetes resources, and it has gotten even easier with better storage class and load balancer support.

    Recommends · Apr 2026 · in “Dear friend, you have built a Kubernetes (2024)”

  10. That was a hell of a lot easier to do with Kubernetes than trying to figure out some giant universe of barely related technologies

    Recommends · May 2026 · in “Should I Run Plain Docker Compose in Production in 2026?”

  11. It's far easier with Kubernetes - just deployment, service secret & ingress config and stuff just works cleanly in namespaces

    Recommends · Jan 2026 · in “Tell HN: DigitalOcean's managed services broke each other after update”

  12. it is not easy to: a) setup and maintain a k8s cluster with all necessary components from at least a dozen different sources

    Mixed · Apr 2026 · in “Google Open Sources Experimental Agent Orchestration Testbed Scion”

  13. Most tasks you would want to do to deploy an application, there's an out of the box solution for k8s that already exists.

    Recommends · Jan 2026 · in “The future of software engineering is SRE”

  14. Or you can just use something that targets a spec to provide a (mostly) cohesive and consistent layer to build upon.

    Recommends · Jun 2026 · in “What job interviews taught me about Kubernetes”

  15. It turns out, Kubernetes was a better fit for a many more use-cases, even beyond large and medium sized enterprises.

    Recommends · May 2026 · in “Clusters become personal (like PCs did)”

  16. it is operationally not that hard to deal with compared to the things I just mentioned, and has a massive ecosystem

    Recommends · Jun 2026 · in “Zero-Downtime Deployments with Docker Compose – No Kubernetes Required”

  17. It's just so much more interchangeable, even if the learning curve for non-SDEs can be a little steeper than VMs.

    Recommends · Jun 2026 · in “What job interviews taught me about Kubernetes”

  18. having to manage a bunch of persistent volumes because most of your applications use sqlite is not very practical

    Mixed · Jul 2026 · in “Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes”

  19. On the application developer side k8s is awesome fo, but the you look inside the box and it melts your face off.

    Mixed · Jun 2026 · in “What job interviews taught me about Kubernetes”

  20. The problem with Kubernetes is that above-average developers can use it to build small things they can't handle.

    Mixed · Jun 2026 · in “Why is Meta destroying its engineering organization?”

  21. I am now using k8s even for small / 'single purpose' clusters just so I can keep renovate/argo/flux in the loop.

    Recommends · Apr 2026 · in “Dear friend, you have built a Kubernetes (2024)”

  22. moving to kubernetes and packing stuff tight on EKS and thus kubernetes has shaved 30% of our costs off already.

    Recommends · May 2026 · in “I returned to AWS, and was reminded why I left”

  23. K8s biggest problem is how relatively heavyweight the kublet is, with memory requirements of roughly half a gig.

    Mixed · Nov 2025 · in “Building the largest known Kubernetes cluster”

  24. 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

    Criticizes · Jun 2026 · in “What job interviews taught me about Kubernetes”

  25. The mental gymnastics required to express oneself in yaml, rather than, say, literally anything else, invariably generates a horror show of extremely verbose boilerplate

    Criticizes · Dec 2025 · in “I Think about Kubernetes”

  26. 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.

    Criticizes · Oct 2026 · in “AI isn't replacing SREs, it's deskilling them”

  27. 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

    Criticizes · Nov 2025 · in “Helm 4.0”

  28. 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.

    Criticizes · Jan 2026 · in “Command-line Tools can be 235x Faster than your Hadoop Cluster (2014)”

  29. If your configuration is megabytes of impossible to understand YAML, and is also not portable to other environments, then what's the point?

    Criticizes · Apr 2026 · in “Dear friend, you have built a Kubernetes (2024)”

  30. K8s is a stack of dozens-to-hundreds of control loops that are built around the idiosyncrasies of a particular distributed key-value store

    Criticizes · Jul 2026 · in “Rebuilding My Homelab with Compose, Ruby, IPv6, and No Kubernetes”

  31. Choosing technologies that require substantial or highly specialised skill sets seems almost routine. I'm looking at you, Kubernetes.

    Criticizes · Jul 2026 · in “Distributed System Is Slower Than a Laptop”

  32. It is overwhelmingly "typical" to the point of extreme eye-rolling when you need to issue "make generate" three dozen times a day

    Criticizes · Dec 2025 · in “Rue: Higher level than Rust, lower level than Go”

  33. Kubernetes is all things to all people and as a result what any given configuration actually does is almost completely random

    Criticizes · Nov 2025 · in “Things I don't like in configuration languages”

  34. to require a full blown K8s cluster already up-and-running with custom operators perfectly configured and working flawlessly

    Criticizes · Jan 2026 · in “OpenGitOps”

  35. People use Kubernetes for way too small things, and it sounds like you don't have the scale for actually running Kubernetes.

    Criticizes · Apr 2026 · in “I Am Building a Cloud”

  36. I'm a Kubernetes user and advocate but to call it "portable" just tells me you've never actually tried to deploy the similar thing on multiple different clouds

    Mixed · Apr 2026 · in “Dear friend, you have built a Kubernetes (2024)”

  37. Huge abstraction layers coming from Kubernetes serve their purpose well, but can screw you up when anything goes slightly wrong on the upper layer.

    Mixed · Dec 2025 · in “Go ahead, self-host Postgres”

  38. K8s is great at keeping things alive. It's not built to reason about whether the thing that's alive is actually working correctly.

    Mixed · Mar 2026 · in “Show HN: Terminal Use (YC W26) – Vercel for filesystem-based agents”

  39. the bottleneck of modern software is not the local network so its not an issue to have these pieces on different bare metal hosts

    Mixed · Jul 2026 · in “Open-weight AI is having its Kubernetes moment. Let's not ruin it”

  40. it provides secure remote configuration and it's that it's platform agnostic, multi-node orchestration, built in load balancing

    Recommends · Dec 2025 · in “Go ahead, self-host Postgres”

Counts from 1,795,640 Hacker News comments, Nov 2025 to Nov 2026. How we count · Report a mistake