Parent: #208
Summary
After severance completes, verify the workload still operates independently. Produce a health report for the operator.
Requirements
- Verify pods are running (no CrashLoopBackOff, no restarts caused by severance) — via EKS for AWS, AKS for Azure
- Verify sites are accessible (HTTP health check on each site's domain)
- Verify Alloy is running and writing to local Mimir (not erroring on missing control room endpoint)
- Verify no control room references remain in active Helm values / deployed config
- Report results: pass/fail per check, with details on failures
- If any check fails, provide actionable guidance (not just "verification failed")
Acceptance Criteria
- Operator gets a clear post-eject health report after severance completes
- Works for both AWS (EKS) and Azure (AKS) workloads
- Any failures include specific remediation steps
- A fully healthy workload reports all checks passing
Parent: #208
Summary
After severance completes, verify the workload still operates independently. Produce a health report for the operator.
Requirements
Acceptance Criteria