Whats The Smallest Setup Where Kubernetes Actually Pays Off?

Solvedarchitecturecontainerskubernetes11 replies · 233 views · started
Accepted solution by Gabe W. — The tipping point is usually multiple services across multiple hosts that need to scale independently, or many teams deploying…
  1. ugh. were a agency running a handful of web apps 🔥 today its Docker Compose on two VMs, deployed by a script. A new hire is pushing hard for Kubernetes: self-healing, rolling updates, industry standard. i worry well spend all our time running the platform instead of the product. wheres the tipping point?

    nobody on the team is a dedicated ops person 🤷 we all write code, and whoever is around handles teh servers. thats teh context Im trying to weigh. any war stories from teams of a similar size would be realy helpful. pls help 🙏

    2
  2. If u do go Kubernetes, keep it boring: one managed cluster, a standard ingress, GitOps for manifests, and resist adding a service mesh until you have a concrete problem it solves.

    19 4 helpful
  3. lol same thing happened to me compose on a VM with a reverse proxy, health checks, restart: unless-stopped, and a simple deploy script covers a surprising amount. what it lacks is multi-host scheduling and zero-downtime deploys without extra work. lmk how it goes

    7 0 helpful
  4. been there man bump... still happening with containers for me worked for me anyway 🤷

    0 2 helpful
  5. hmmmm ok reading this at 2am instead of sleeping, no regrets. honestly just reset the router and save yourself teh pain

    0 1 helpful
  6. manaegd Kubernetes removes the control plane work, but you still own node upgrades, ingress, cert management, secrets, monitoring and teh version upgrade treadmill lol budget real time for that every quarter. lmk how it goes

    0 2 helpful
  7. uhh which version are you on?

    thinking

    5 1 helpful
  8. hmmm dumb question but how do i even check the default config

    thinking

    5 0 helpful
  9. The tipping point is usually multiple services across multiple hosts that need to scale independently, or many teams deploying independently. If client websites fits on one or two machines, the benefits are small.

    1 8 helpful
  10. yesss finally got it working, thx everyone, pro tip: write down what u change... i didnt and had to redo agency from scratch thank u thank u thank u

    9 2 helpful
  11. @gwolfe WOWWW well try managed Kubernetes for teh API only, with strict keep it boring rules. thanks for the grounded advice. thank u thank u thank u

    25 0 helpful

Reply to this topic

Sign in or create an account to reply.