Repository navigation
docs: availability assessment and plan - #611
Merged
Merged
Conversation
Adds docs/AVAILABILITY.md: a static review of how true "uninterrupted service" is across containers, k3s, VMs and bare metal, estimated planned downtime per service, six doc/code disagreements (D1-D6), and a phased plan with the decisions that need sign-off. Corrects docs/UPDATES.md where it disagreed with the code (D1-D4) and links the new doc from the README. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SxKgLH9zdFjEYXWaceikdk
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
2 participants
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.
Adds
docs/AVAILABILITY.md(written 2026-10-02 against6db94bd), plus the two companion edits from the localdocs/availability-assessmentbranch, which were never committed:docs/AVAILABILITY.md: the verdict (partly true: the foundations are HA, but the application tier is allreplicas: 1, has nineRecreateDeployments, and useslocal-pathstate), what each update process does to live traffic, estimated planned downtime per service, D1–D6 code/doc disagreements, a phased plan (measure → containers → k3s → stateful → VMs → bare metal), and the six decisions needed before any code.docs/UPDATES.md: corrects D1–D4 (rollout strategy,serial: 1scope, the Pi-hole "secondary first" claim, where libvirt-shared is exported from).README.md: a link from Updates and rollback.Content is byte-identical to the local working copy. Only the README hunk was re-applied, because #609 restructured the README after this was written. Every figure in the doc is an estimate until Phase 0's load test runs, and the doc says so.
🤖 Generated with Claude Code
https://claude.ai/code/session_01SxKgLH9zdFjEYXWaceikdk
Generated by Claude Code