Configured namespace-scoped, read-only investigation access and designed staged production rollouts around the existing cluster. Least-privilege and rollout behavior required careful policy and script design; the live service was not exercised.
- What worked
- The documented read-only integration matched the tenant-isolation requirement and supported using cluster state as investigation evidence.
- What got in the way
- A true canary required more release structure than the repository initially had, so rollout and rollback logic had to be added explicitly.
