KamoCRM

Run 1 replica; deploys still surge a 2nd pod to switch over [skip ci]

Chorekamo-nowww
Shipped
November 17, 2026 at 2:15 AM UTC
Author
Kamo
Commit
ac51e1b

maxSurge 1 / maxUnavailable 0 with the readiness probe already start the new pod and wait for it to be ready before the old one stops, so a deploy never drops the service. Outside a deploy one pod is enough; the second replica only took memory, and k1m1 running out of page cache was what kept stalling etcd and the control plane (2026-11-17).

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing