Managed Kubernetes Changed My Mind. Or Did It??

architecturecontainerskubernetes9 replies 路 297 views 路 started
  1. question for people who've been through it: for a agency with a couple of APIs and a database, did moving to Kubernetes pay off? i'm interested in the operatinoal reality: upgrades, debugging, on-call, not the conference talk version.

    im not against Kubernetes in principle. i just want to know what the day-to-day reality looks like for a team our size: how much time goes into upgrades, debugging the platform, and on-call compared to before. pls help 馃檹

    1
  2. ok but does anyone on teh four-person team already have hands-on Kubernetes experience?

    1 0 helpful
  3. have u checked ur couple settings? mine were reset after an update.. lmao following, having teh same problem good luck man!

    0 1 helpful
  4. ahh classic 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. hope that helps :)

    4 2 helpful
  5. btw page 1 lets gooo :)

    0 1 helpful
  6. ok so managed Kubernetes removes the control plane work, but you still own node upgrades, ingress, cert management, secrets, monitoring and teh version upgrade treadmill... budget real time for that every quarter. hope that helps :)

    thinking

    0 1 helpful
  7. ahh classic 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 schedluing and zero-downtime deploys without extra work.

    1 0 helpful
  8. exact same thing happened to my old thinkpad last month. try turning off the extension first, fixed it for me lmk how it goes

    21 0 helpful
  9. ehh counterpoint: Nomad or Swarm give you multi-host scheduling with a fraction of the complexity ;) dont treat it as Compose vs Kubernetes only.

    0 1 helpful

Reply to this topic

Sign in or create an account to reply.