问HN：在2025年，Kubernetes对于初创阶段仍然是个大忌吗？
人们常常说，早期阶段的初创公司应该尽量避免使用K8s。我曾经在裸金属基础设施上管理过它，因此我理解这种观点的来源——Kubernetes在历史上确实很难设置，你需要花费大量时间学习相关概念以及如何编写YAML配置等。
然而，近年来托管的K8s选项有了显著改善（所有云服务提供商几乎都有自我管理的Kubernetes选项），而且我觉得借助大型语言模型（LLMs），阅读和编写部署配置变得极其简单。
你对在早期阶段（比如，当你有初步的客户适配和一个5人以上的工程团队时）采用K8s作为基础设施并围绕它进行标准化有什么看法？什么情况下算是太早？你认为现在仍然存在哪些陷阱？
查看原文
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.<p>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.<p>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?