TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Anyone using DigitalOcean K8s (DOKS) in production?

3 点作者 Syntaf将近 2 年前
I&#x27;ve been hosting small projects on DOKS for the past 2 years without any issue, but I seldom come across mentions of DOKS online compared to GKE &#x2F; EKS - is there any reason why?<p>On a 3-node cluster running the cheapest node-tiers available I generally have no issue handling a couple thousand requests a day on my hobby sites, which doesn&#x27;t necessarily say much, but pretty soon here I&#x27;m going to be launching a real product with my co-founder.<p>I&#x27;d like to stick with DOKS because of my familiarity, but I also don&#x27;t want to stick with a technology that&#x27;s going to come back to bite us if it turns out we can&#x27;t scale with it.<p>If anyone has experiences or opinions here, please share!

1 comment

hitpointdrew将近 2 年前
I have never used DOKS, but I wouldn’t really fret or worry it if I were you. You are using a managed k8s cluster, you should have everything you have deployed to it in git, and ideally something like Argo or helmfile where you could redeploy everything pretty easily.<p>If you need to pivot it should not be very hard, your not managing your own k8s cluster where you would needed to rework Terraform code for a new cloud provider, and learn the idiosyncrasies of setting up the cloud control manager, adding storage classes etc.<p>Since you are using managed k8s, I wouldn’t even think about DOKS, EKS, or GKE. Those are pretty irrelevant, at the end of the day you are using Kubernetes. Nothing you do in one can’t be used in another, your deployments, services, secrets, configmaps, ingresses, etc. are all going to be the same no matter your provider.<p>The biggest pain point with switching cloud providers (if you had to) would be migrating your database (assuming you have one).