Canary and operate health checks

From a fresh clone/directory, run the commands that prove vector pause → readyz 503, livez 200, no restart loop; process deadlock → livez fails → restart. A second person plays cluster operator during vector DB maintenance window and follows your script without coaching. The demo includes limitations: what Kubernetes liveness vs readiness for retrieval-and-generation API still will not do.

Bundle: contract snippet, passing tests, metric snapshot for restart_count == 0 during dep outage and ready_pods ≥ 1 when deps healthy, security negative probe, rollback note, owner name. Reference PROBE-RESTART-STORM-8 as the drill you rehearsed. If any item is missing, the ship gate fails even if the happy path dazzles.

For Health check lab, name the human who gets paged, the review date for thresholds, and the condition that triggers reevaluation. Endpoint GET /livez and GET /readyz remains the production surface you operate for Kubernetes liveness vs readiness for retrieval-and-generation API — not a slide. Keep PROBE-RESTART-STORM-8 in the handoff template so the next owner inherits the drill.

After the peer demo, schedule the next threshold review date. File a short changelog that mentions PROBE-RESTART-STORM-8 and the control that addresses it. Archive the evidence pack where your team already stores launch records. Resist rewriting everything “for real production” in one weekend — operate this slice until the metrics bore you, then widen. Final self-check: if telemetry vanished, would you still know to hold? If yes, you learned the operating posture this lane teaches.

Trim the demo script until every command is necessary. Record a peer signature line: name, date UTC, pass/fail. File known limitations as bullets, not apologies. Link the evidence pack from the README. Schedule the next game day on a calendar, even if it is solo. Archive the branch tag or release digest you actually shipped. In this chapter the product is Kubernetes liveness vs readiness for retrieval-and-generation API, the human stakeholder is cluster operator during vector DB maintenance window, and the incident id you design against is PROBE-RESTART-STORM-8. Re-state the oracle in your notes — vector pause → readyz 503, livez 200, no restart loop; process deadlock → livez fails → restart — and keep the invariant visible: /livez only checks process; /readyz checks vector+model deps; wrong probe kills healthy pods. Track restart_count == 0 during dep outage and ready_pods ≥ 1 when deps healthy as the scoreboard. Surface under change control: GET /livez and GET /readyz. If you only have forty minutes, finish the fixture for readyz embedded in liveness → restart storm during dependency blip before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.