deploy: two replicas, surge rollout, requests sized to use

A pod that is not ready took every caller behind the gate dark, and
every rollout this week left a five-minute 503 in the watchdog log.
Two replicas with maxSurge 1 / maxUnavailable 0 keep one Ready pod
through a rollout or a crash. One node: this covers rollouts and pod
failures, not the node.

The node has 1700m CPU allocatable with 1470m requested; a second pod
at the old 450m request could not schedule (tablet 31 saw the surge
pod hang Pending). The pod USES 22m (vav 20m, sidecars 2m, measured),
so requests move to what is used with headroom: vav 120m/256Mi,
sidecars 40m/64Mi — 200m per pod, 400m for two, less than the one pod
asked before. Limits unchanged. POOL_SIZE 10 → 5 per pod (10 in all,
under the hobbyist tier's ceiling). KOHEN "Rolling out" updated.

Both manifests validate (kubectl --dry-run=client). Doorpost pin
unchanged. Applying needs the transmitter (or the classifier off).

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

deploy/k8s/deployment.yaml

@@ -18,18 +18,25 @@ metadata:
     app.kubernetes.io/name: shorashim
     app.kubernetes.io/version: "0.1.0"
 spec:
-  replicas: 1
-  # One replica on one node with no room to surge. The default
-  # (maxSurge 25% → 1 extra pod) asks for 450m CPU the node does not
-  # have beside the running pod, and the rollout hangs Pending while the
-  # old image keeps serving (tablet 31, 2026-10-04). Replace in place.
-  # The new pod reads the day's manna from the manna-pvc volume; it is
-  # Ready again without the kohen, as long as today's portion was written.
+  # Two replicas (2026-10-25). A pod that is not ready took every caller
+  # behind the gate dark, and every rollout left a five-minute 503 in
+  # the watchdog log; with two pods and a surge rollout the Service keeps
+  # one Ready pod throughout. One node: this covers rollouts and pod
+  # crashes, not the node. The node has 1700m CPU allocatable and 1470m
+  # was requested (tablet 31, 2026-10-04: a surge pod at 450m hung
+  # Pending), so the requests below are sized to what the pod USES
+  # (vav 20m, sidecars 2m, measured) with headroom — 200m per pod, 400m
+  # for two — not to the old 450m. Limits are unchanged. Each pod reads
+  # the day's manna from the manna-pvc volume and is Ready without the
+  # kohen as long as today's portion was written; the database pool is
+  # 5 per pod (POOL_SIZE in the ConfigMap), 10 in all, under the
+  # hobbyist tier's ceiling.
+  replicas: 2
   strategy:
     type: RollingUpdate
     rollingUpdate:
-      maxSurge: 0
-      maxUnavailable: 1
+      maxSurge: 1
+      maxUnavailable: 0
   selector:
     matchLabels:
       app.kubernetes.io/name: shorashim
@@ -237,7 +244,7 @@ spec:
           resources:
             requests:
               memory: "256Mi"
-              cpu: "250m"
+              cpu: "120m"
             limits:
               memory: "1Gi"
               cpu: "1000m"
@@ -293,8 +300,8 @@ spec:
               mountPath: /tmp
           resources:
             requests:
-              memory: "128Mi"
-              cpu: "100m"
+              memory: "64Mi"
+              cpu: "40m"
             limits:
               memory: "512Mi"
               cpu: "500m"
@@ -318,8 +325,8 @@ spec:
               mountPath: /tmp
           resources:
             requests:
-              memory: "128Mi"
-              cpu: "100m"
+              memory: "64Mi"
+              cpu: "40m"
             limits:
               memory: "512Mi"
               cpu: "500m"