Staging Rollout Plan
This plan covers how to roll out the updated Boss Agent ADK in staging while keeping traffic safe and maintaining observability. All routing and tool discovery must come from the Boss Agent ADK MCP server (the single source of truth).
1. Deploy Updated Boss Agent
- Build and deploy the new Boss Agent ADK revision to the staging Cloud Run service, ensuring the embedded MCP server (tool/registry source of truth) starts successfully.
- Verify startup logs and
/healthpass in staging for both the ADK container and the MCP server backing the Boss Agent tools. Keep the prior revision with a small traffic slice (e.g., 10%) for quick rollback.
2. Shadow Traffic for Parity
- Enable shadow (mirrored) traffic from the API Gateway to the new Boss Agent ADK revision.
- Compare responses, latency, and registry health checks between mirrored and primary paths.
- Gate production promotion on parity metrics: request success rate, average latency, registry/adapters returning healthy statuses, and MCP server schema parity with toolbox definitions.
3. Validate and Retire Redundant Routing
- Once parity thresholds are met, shift staging traffic incrementally (25% → 50% → 100%).
- Remove redundant Cloud Run routing entries and deprecate the legacy (non-ADK) Boss Agent revisions in staging.
- Capture a final health snapshot (registry + adapter routes) and MCP server tool availability before locking the routing table.
4. Promotion Readiness
- Freeze staging for 30–60 minutes to observe for regressions.
- Document the finalized routing map and registry endpoints, then proceed with production rollout following the same staged steps.