Drain API pods before Kubernetes shutdown

2026-08-05 21:55:32 +02:00
parent 3b9ae901dd
commit 389df7c3d5
3 changed files with 39 additions and 0 deletions
@@ -270,6 +270,10 @@ record under the installation evidence directory and never retains the API key.

 Use `--exercise-api-pod-loss` in an approved drill window to delete one API pod,
 observe the public readiness path continuously, and record its replacement.
+Generated API workloads use a ten-second pre-stop drain so Kubernetes can remove
+the terminating endpoint from ingress and service routing before Uvicorn exits.
+Do not remove or shorten this drain without repeating the public-path pod-loss
+test against the target ingress controller and network implementation.
 This proves the bounded stateless-node-loss slice only. Session continuity,
 accepted-job redelivery, state-service failover, and coordinated restore remain
 separate target exercises whose signed evidence is governed by