4 ms·

As a start-up*, you shouldn't use Kubernetes managed by GKE, EKS, etc; you should use bare metal Kubernetes: "server rack" somewhere near your desk, 3 virtualiz

As a start-up*, you shouldn't use Kubernetes managed by GKE, EKS, etc; you should use bare metal Kubernetes: "server rack" somewhere near your desk, 3 virtualized nodes with Ubuntu, MetalLB as load balancer, local-storage StorageClass with cron backups on another machine, Prometheus with Grafana for monitoring, CertManager DNS01 with Let's Encrypt for SSL, Contour/Traefik for routing, self host Docker registry, self host CI, Minio for object storage, Mongo/Postgres/etc. for database, Redis for caching. First setup time: 1-2 days, maybe one week to work out the kinks. Initial cost: ~$500 for a refurbished Dell/HP server, or go extreme with 3 RaspberryPis. Monthly cost: local electricity price, internet monthly fee. Current uptime with the above setup: 139 days (had a power outage 139 days ago, previous uptime was around 200 days). * start-up: endeavour started with negative, $0, or close to $0 in bank counting time to market in years; not a start-up (maybe a start-middle): company with millions in VC money hoping for time to market yesterday.

wikibob 4y ago
Is this satire? A startup should ruthlessly prioritize doing only the one single thing that drives revenue, which is not bespoke infrastructure configuration.
- ly3xqhl8g9 4y ago
  Check the given definition for start-up. A start-up doesn't have $200+/month for managed Kubernetes, cloud storage, cloud CI/CD pipelines, CDNs and all the other niceties. Also, not all start-ups are born in Silicon Valley or nearby, nevertheless 90% of all start-ups fail, some of them because they waste money on cloud infrastructure while hallucinating time to market tomorrow and are unable to be lean, duct taping and WD-40-ing (soon ChatGPT-ing) some disposable infrastructure for pennies.
  - JamesSwift 4y ago
    I can guarantee you that they are wasting more than 200/month of an engineers time and mental energy to manage the bare metal setup vs the cloud managed offering. Its penny wise and pound foolish.
    - ly3xqhl8g9 4y ago
      I am a one-man start-up, well, trying to be for some years now, and I run a similar bare metal setup as the one above. Haven't touched it in 142 days and it costs next to nothing vs. the $200/month that I couldn't afford even if I wanted. Again, maybe the word 'start-up' has too many meanings. Sure, once you have 1,000+ paying clients you will be able and even you will need to rely on cloud infrastructure, but 90+% of start-ups never reach 1,000+ paying clients. And again, it's not that complicated, pretty much everything is a Helm chart, and when you are merely trying things out, not even close to product-market fit or monthly recurring revenues, you can afford to have the cluster down for days on end: there is no one to care.
- wtfbbqsms 4y ago
  These are all industry-standard tools that you could also run outside k8s in docker-compose, I fail to see anything bespoke here. If your team cant recognize some of the most common proxy, s3 storage, database, operating system, cron job, backups, load balancing tools from a few feet away or manage a server then you have a problem with vetting candidates.
JamesSwift 4y ago
I wouldn't recommend anyone manage the control plane except after hitting massive scale and being able to dedicate engineers to it full time. For a startup, I would doubly recommend against it. Thats the fastest way to give back all the time you've saved in using k8s in the first place. Yes its more expensive, thats the tradeoff and I 100% believe its worth it.

wikibob 4y ago

Is this satire? A startup should ruthlessly prioritize doing only the one single thing that drives revenue, which is not bespoke infrastructure configuration.

ly3xqhl8g9 4y ago
Check the given definition for start-up. A start-up doesn't have $200+/month for managed Kubernetes, cloud storage, cloud CI/CD pipelines, CDNs and all the other niceties. Also, not all start-ups are born in Silicon Valley or nearby, nevertheless 90% of all start-ups fail, some of them because they waste money on cloud infrastructure while hallucinating time to market tomorrow and are unable to be lean, duct taping and WD-40-ing (soon ChatGPT-ing) some disposable infrastructure for pennies.
- JamesSwift 4y ago
  I can guarantee you that they are wasting more than 200/month of an engineers time and mental energy to manage the bare metal setup vs the cloud managed offering. Its penny wise and pound foolish.
  - ly3xqhl8g9 4y ago
    I am a one-man start-up, well, trying to be for some years now, and I run a similar bare metal setup as the one above. Haven't touched it in 142 days and it costs next to nothing vs. the $200/month that I couldn't afford even if I wanted. Again, maybe the word 'start-up' has too many meanings. Sure, once you have 1,000+ paying clients you will be able and even you will need to rely on cloud infrastructure, but 90+% of start-ups never reach 1,000+ paying clients. And again, it's not that complicated, pretty much everything is a Helm chart, and when you are merely trying things out, not even close to product-market fit or monthly recurring revenues, you can afford to have the cluster down for days on end: there is no one to care.
wtfbbqsms 4y ago
These are all industry-standard tools that you could also run outside k8s in docker-compose, I fail to see anything bespoke here. If your team cant recognize some of the most common proxy, s3 storage, database, operating system, cron job, backups, load balancing tools from a few feet away or manage a server then you have a problem with vetting candidates.

JamesSwift 4y ago

I wouldn't recommend anyone manage the control plane except after hitting massive scale and being able to dedicate engineers to it full time. For a startup, I would doubly recommend against it. Thats the fastest way to give back all the time you've saved in using k8s in the first place. Yes its more expensive, thats the tradeoff and I 100% believe its worth it.