Jean-Gabriel Gill-Couture
13e5549d6b
All checks were successful
Run Check Script / check (pull_request) Successful in 2m22s
Adds the operator_restart integration test that gates scenario #1 in docs/fleet-operator-recovery-scenarios.md: when the operator Pod is killed and replaced, the new instance must rebuild Deployment status + desired-state KV from NATS alone, byte-for-byte matching the pre-kill snapshot within 30 s. Pattern: deploy via FleetOperatorScore (no handrolled manifests), seed a Device + Deployment CR, wait for first patch, snapshot the aggregate counts + desired-state bytes, delete the operator pod, wait for the replacement Ready, then poll the snapshot until it matches or the budget elapses. Gated behind HARMONY_FLEET_E2E=1 so cargo test --workspace stays cheap; runs in its own test binary to isolate the pod-kill blast radius from the existing operator suite. Step 2 of v0.3 Chapter 2. Steps 3-5 deferred.