Description
The upgrade guide is a useful version-by-version migration ledger but does not give one reusable operational procedure for preflight, rollout verification, persistence, or rollback.
Acceptance Criteria
- #1 The guide covers persistence backup considerations, -validate, redacted effective-config review, controlled restart, readiness, and post-upgrade OTLP or Prometheus verification
- #2 It distinguishes safe rollback from migrations that require the documented forward-recovery path
- #3 Version-specific entries link to the reusable checklist instead of duplicating it
Definition of Done
- #1 go build ./… && go vet ./… && go test -race ./…
- #2 golangci-lint run
- #3 scripts/regen-generated.sh (only if a generated artifact’s inputs changed)
Implementation Plan
Add one reusable upgrade-and-rollback checklist, link version-specific entries to it, and preserve forward-only recovery for flow-store adoption.
Implementation Notes
The reusable upgrade and rollback checklist is committed in bundled pause snapshot 2cf46446d5c6a7a30ea6f7d0c54d61ec9889d522 and the docs checker passed. Resume with exact-head CI and an operational exercise when desired.
Final evidence: documentation checker, integrated GATE, and exact-head CI run 33047209645 passed. The live campaign exercised controlled restart, readiness, Prometheus verification, and an Alloy restart with persistent recovery.
Final Summary
Upgrade and rollback guidance is committed in 2cf46446d5c6a7a30ea6f7d0c54d61ec9889d522; parked pending exact-head CI and operational proof.
Completion: verified by documentation checks, exact-head CI, and live restart/readiness exercises.