Secure load testing operations

Separate runtime and operator roles for k6 streaming load test for chat completion gateway. Runtime may only perform the narrow actions that capacity planner before Black Friday traffic 3× baseline needs; operators get audited break-glass with TTL. Encode a negative probe that denies the privilege trick related to load generator retries hide server shedding — false green.

Redact prompts/PII at collection. Secrets enter via a manager or workload identity — never source, fixtures, or exception strings. Incident LOAD-FALSE-GREEN-33 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: abort if error_rate > 1% or p95_ttft > 1.5s; test cost ≤ $50.

Abuse cases unique to this lab include the privilege path implied by load generator retries hide server shedding — false green. 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 k6 streaming load test for chat completion gateway 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 k6 streaming load test for chat completion gateway, the human stakeholder is capacity planner before Black Friday traffic 3× baseline, and the incident id you design against is LOAD-FALSE-GREEN-33. Re-state the oracle in your notes — find saturation knee near 180 RPS; beyond that queue depth explodes — and keep the invariant visible: abort if error_rate > 1% or p95_ttft > 1.5s; test cost ≤ $50. Track saturation_rps, p95_ttft_ms, test_usd as the scoreboard. Surface under change control: POST /v1/chat/completions (stream). If you only have forty minutes, finish the fixture for load generator retries hide server shedding — false green before polishing UI. Promotion language stays ternary: promote, hold, or roll back based on evidence, not hope.