The manifest said cpu 2 / memory 6Gi while the live StatefulSet ran cpu 3 /
memory 7Gi, so `kubectl apply -k k8s/cluster/` DOWNGRADED production every time
it was run - a silent capacity regression on the write path, delivered by the
very command used to deploy a fix. Verified before and after with kubectl diff:
the cpu/memory hunks are now absent, so an apply is a no-op on resources.
The live values are the intended ones; this file is now the source of truth for
them. The comment keeps the reasoning that matters - the limit exists to keep the
measured query/apply burst reachable without reserving it, and when neighbours
burst too the answer is more REQUEST, not more limit, because CFS throttling is
how CockroachDB was pushed into multi-second Raft stalls on this fleet with nodes
70% idle.
c9adec040d