Nobody needs Kubernetes for eleven users
joshuaajayi
21 points
3 comments
July 22, 2026
Related Discussions
Found 5 related stories in 62.3ms across 5,804 title embeddings via pgvector HNSW
- Cheap self-hosted Kubernetes on Hetzner cloud (2025) victorbrink · 61 pts · July 21, 2026 · 50% similar
- Kubernetes on Oxide: How customer needs shaped our integrations stevehipwell · 176 pts · August 13, 2026 · 47% similar
- Open-weight AI is having its Kubernetes moment tknaup · 355 pts · July 25, 2026 · 45% similar
- Show HN: Managing on-premise servers without Kubernetes r2ob · 16 pts · July 26, 2026 · 45% similar
- K0s – The Zero Friction Kubernetes porjo · 11 pts · July 21, 2026 · 44% similar
Discussion Highlights (2 comments)
arjie
I find containerization useful regardless and Kube allows a simple orchestration solution so I can use a single machine for many things without too much trouble. No need to worry too much about ports and log rotation and all that. Just a nice batteries-included solution. The primitives are also trivial to reason about. And writing YAMLs sucked in the old days but now with kustomize built in you can easily do everything you want with templating. LLMs can write it all. As an aside, please prompt your agent to be more concise. Totally unnecessary text expansion. “I didn’t do this to be clever”. Pure filler text. No one talks like this.
bad_username
> Microservices solve a real problem too, and it is mostly organisational rather than technical. When you have enough engineers that they are stepping on each other in one codebase, and enough teams that release schedules collide, splitting the system along team boundaries buys independence. grug wonder why big brain take hardest problem, factoring system correctly, and introduce network call too seem very confusing to grug