Repository navigation
Document batch upgrade boundaries and S3 readiness checks - #56
Merged
Merged
Conversation
Signed-off-by: Feng Ruohang <rh@vonng.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
SILO 20261109 batch manifests and authorized reports cannot be resumed by 20261026. Add bilingual drain, cancellation, resubmission and rollback instructions at the batch and upgrade entry points.
Clarify that neither
readynor cluster quorum alone guarantees a restarted node can serve S3; document bounded per-node write/read checks and preserve peer bootstrap. Correct the conflicting Compose guidance. Refreshed the site counters withbin/metrics.py.Validation:
make checkpassed (Hugo build, Python checks and internal links).