Skip to content

Commit eedd3da

Browse files
Thomas TupperThomas Tupper
authored andcommitted
docs: require non-zero watchtower scan coverage before promotion
1 parent 3eeeeb9 commit eedd3da

1 file changed

Lines changed: 5 additions & 0 deletions

File tree

docs/WATCHTOWER_PHASE1_MONITOR_ONLY.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,8 +50,13 @@ Containers without label remain out of scope in phase 1.
5050
5151
- At least 24h of clean monitor-only operation.
5252
- No unexplained restarts in critical stack.
53+
- Coverage proof is non-zero: at least one completed scan cycle with `Scanned > 0` for intended labeled scope (not just startup logs).
5354
- Explicit go/no-go decision recorded in deployment notes.
5455

56+
## Scan-timing caveat (important)
57+
58+
Watchtower periodic mode can appear healthy before the first full scan completes. Startup logs alone are not evidence of scope coverage. Always capture at least one post-interval session summary (`Failed/Scanned/Updated`) and treat `Scanned=0` as a configuration/scope blind spot that must be fixed before promotion.
59+
5560
## Source
5661

5762
- Watchtower docs: https://containrrr.dev/watchtower/container-selection/

0 commit comments

Comments
 (0)