Sign in

Is Kubernetes Overkill For A Two-Person Team Running Client Websites??

architecturecontainerskubernetes5 replies 路 198 views 路 started
Reply
  1. Hana Ueda
    @binaryshed

    help!! question for ppl whove been through it: for a two-person team with client websites, did moving to Kubernetes pay off? im interested in the operational reality: upgrades, debugging, on-call, not the conference talk version.

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

    2
  2. Zane Z.
    @zzhang

    hmmmm quick q what actually hurts today: deployments, scaling, outages, or smth else?

    1 0 helpful
  3. Hana Ueda
    @binaryshed
    in reply to @zzhang

    A few seconds is tolerable for most of client websites, but not for the API. sorry for the wall of text lol

    cry

    0 6 helpful
  4. Nell Rossi
    @ping_bench

    ok so a PaaS or a managed container service gives u most of teh rolling-deploy and self-healing benefits with far less surface area. Consider it before jumping straight to raw Kubernetes.

    3 0 helpful
  5. Esme R.
    @esmer74

    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 scheduling and zero-downtime deploys without extra work. lmk how it goes

    12 1 helpful
  6. Alba B.
    @albab915

    i'd argue learning Kubernetes is a good long-term investment even for a solo developer setup; skills and tooling transfer everywhere.

    1 0 helpful

Reply to this topic

Sign in or create an account to reply.