Skip to main content
Phase 5 promises one test per failure mode. This page maps each scenario to the tests that prove it, so a gap is visible instead of assumed. Every fast test also asserts the level-triggered property: after recovery, one more reconcile pass is a no-op (no create, start, stop or remove). Fast tests use the fake Docker client with injected failures and run under go test -short. Live tests need a Docker daemon, live in _live_test.go files, and skip under -short; the nightly run executes them.

Matrix

Known gaps

None found by this pack. These are limits of what the tests prove, not failing tests:
  • The two live tests inject the daemon and disk faults at the runtime boundary on top of a real daemon. They do not stop dockerd or fill a real filesystem, because that would take down the nightly host.
  • Agent severing is exercised with a fake transport and a fake gRPC stream, not a real mTLS connection. The real-agent reconnect path is measured in test/e2e/reconcile (break_glass_agent_reconnect_test.go).
  • Disk full is proven at the points a deploy writes (pull, start, volume, build, log, metric). A full disk under the Caddy certificate store or the backup writer has its own guards and is not part of this pack.
Last modified on October 23, 2026