ci: re-trigger build

fix(docs): set terminationGracePeriodSeconds to 120 in Kubernetes YAML example
The example showed terminationGracePeriodSeconds: 30, but the accompanying note says the value "should exceed the healthcheck failure threshold (3 × 30s = 90s)". With 30s < 90s, Kubernetes would send SIGTERM and wait only 30s before SIGKILL — potentially killing the pod before the graceful shutdown (3s via stop_event) completes. Changed to 120s, which exceeds the 90s threshold and aligns the YAML example with the documented requirement. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-15 05:29:15 +00:00 · 2026-05-15 04:57:26 +00:00
1 changed files with 2 additions and 2 deletions
@@ -186,10 +186,10 @@ readinessProbe:
  periodSeconds: 10
  timeoutSeconds: 5
  failureThreshold: 3
-terminationGracePeriodSeconds: 30
+terminationGracePeriodSeconds: 120
 ```

-> **Note:** The Kubernetes `terminationGracePeriodSeconds` should exceed the healthcheck failure threshold (3 × 30s = 90s) to allow the liveness probe to fail before the pod is killed.
+> **Note:** `terminationGracePeriodSeconds` must exceed the liveness probe failure window (3 × 30s = 90s) so that Kubernetes sends SIGTERM and allows graceful shutdown before the pod is killed. The 120s value here gives a 30s buffer beyond the 90s threshold.

 ## Troubleshooting