Set secrets, auth, and blast-radius boundaries

Separate runtime and operator roles for containerized café FAQ RAG with readiness probes and versioned index pin. Runtime may only perform the narrow actions that platform engineer shipping faq-index@sha256:a1b2 to staging needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to new pods serve empty index while old pods terminate — citation miss spike.

Redact prompts/PII at collection. Secrets enter via a manager or workload identity — never source, fixtures, or exception strings. Incident DEPLOY-EMPTY-INDEX-5 should be impossible if these controls hold. Output allowlists and schema checks stay in force on error paths.

Rehearse the rollback or kill switch timed against a clock. Record actor, reason, prior revision/secret/flag, and verification query. Invariant reminder: readyz fails if index digest ≠ pinned digest; rollback restores previous digest in < 2 min.

Abuse cases unique to this lab include the privilege path implied by new pods serve empty index while old pods terminate — citation miss spike. Prove a read-only role cannot mutate. Break-glass tokens expire; leftover tokens fail the drill. Dependency pin/digest story matters when images or models move under you. Document how to rotate the credential that containerized café FAQ RAG with readiness probes and versioned index pin uses without a full outage window longer than your dual-run plan. Security evidence is part of ship, not an appendix nobody reads.

List network egress destinations and justify each. Ensure debug endpoints are off by default in the shipping config. Verify that error responses do not echo secrets or raw stack frames to clients. For multi-tenant paths, add a cross-tenant probe fixture. Time the rollback drill twice — once with the author, once with a peer. Store the drill transcript beside the threat notes for the incident id. In this chapter the product is containerized café FAQ RAG with readiness probes and versioned index pin, the human stakeholder is platform engineer shipping faq-index@sha256:a1b2 to staging, and the incident id you design against is DEPLOY-EMPTY-INDEX-5. Re-state the oracle in your notes — kubectl rollout status shows ready; /readyz 200 only when index pin matches — and keep the invariant visible: readyz fails if index digest ≠ pinned digest; rollback restores previous digest in < 2 min. Track ready_ratio == 1 and citation_miss_rate ≤ 0.02 during rollout as the scoreboard. Surface under change control: GET /readyz. If you only have forty minutes, finish the fixture for new pods serve empty index while old pods terminate — citation miss spike before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.