Do I Need Kubernetes?
Posted4 months agoActive4 months ago
doineedkubernetes.comTechstory
calmpositive
Debate
40/100
KubernetesContainer OrchestrationDevops
Key topics
Kubernetes
Container Orchestration
Devops
The discussion around whether one needs Kubernetes revolves around its benefits for scaling, deployment automation, and reliability, with many commenters sharing their positive experiences with Kubernetes and related tools.
Snapshot generated from the HN discussion
Discussion Activity
Moderate engagementFirst comment
2h
Peak period
10
0-6h
Avg / period
3.2
Comment distribution16 data points
Loading chart...
Based on 16 loaded comments
Key moments
- 01Story posted
Sep 13, 2025 at 8:59 PM EDT
4 months ago
Step 01 - 02First comment
Sep 13, 2025 at 10:56 PM EDT
2h after posting
Step 02 - 03Peak activity
10 comments in 0-6h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 16, 2025 at 2:46 AM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45236574Type: storyLast synced: 11/20/2025, 4:11:17 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
Honestly. Give yourself a month to learn it and migrate your home lab and it's actually not too difficult. Yes it takes a lot of debugging initially, but like most things, once you're familiar, it becomes easy.
And that’s an undeniable feature of Kubernetes: people know about it, and smart people use the same (CNCF) building blocks, to keep maximising the probability that your next Kubernetes engineer has also knows about it.
But do you want to turn your software system distributed at the cost of immense complexity?
Only if you’re already cultivating something immensely complex, and you’d be better off with a common language.
If your needs are met by a VM or three then sure, you may not need Kubernetes, although as other comments have pointed out, distributions like k3s can be useful even in those environments. But as you climb the scale and complexity ladder, there soon comes a point where it's very hard to beat Kubernetes, which is why it has become so widespread.
> It isn't about the tooling, it's knowing the business.
The sort of statement I expect to see on LinkedIn. Once you know the business, you decide on appropriate tooling. As I said, as you climb the scale and complexity ladder, Kubernetes starts to make more sense. At that point, the tooling can become very important.
https://news.ycombinator.com/item?id=735568