It's a commonly-repeated comment that early stage startups should avoid K8s at all cost. As someone who had to manage it on a baremetal infrastructure in the past, I get where that comes from - Kubernetes has been historically hard to setup, you'd need to spend a lot of time learning the concepts and how to write the YAML configs, etc.
However, hosted K8s options have improved significantly in recent years (all cloud providers have Kubernetes options that are pretty much self-managed), and I feel like with LLMs, it's become extremely easy to read & write deployment configs.
What's your thoughts about adopting K8s as infrastructure early on (say, when you have initial customer fit and a team of 5+ engineers) and standardizing around it? How early is too early? What pitfalls do you think still exist today?
Comments URL: https://news.ycombinator.com/item?id=44976292
Points: 8
# Comments: 2
Zaloguj się, aby dodać komentarz
Inne posty w tej grupie

I first posted Splice CAD as an in-browser tool for making cable harnesses.
Since then it’s grown in both features and scope — the direction is moving from “harness-only” toward a lightweight CA

Article URL: https://ips-dc.org/report-executive-excess-2025/

Article URL: https://giansegato.com/essays/probabilistic-era

Article URL: https://github.com/ghostty-org/ghostty/pull/8289