Use this checklist before any fleet patching operation. Work the structured items above; every critical item must be confirmed before the first wave starts.
Capturing a usable baseline
A baseline is only useful if the post-patch check can compare against it. Record the numbers somewhere the next operator can read, not in your terminal scrollback.
Capture at minimum: health-endpoint status and latency, error rate over the last hour, running kernel, and the versions of the packages you are about to change. The kernel and package versions are what let the post-patch check prove the change landed.
Sign-off
- Operator: _________________ Date: ___________
- Reviewer: ________________ Date: ___________