docs(cluster-upgrade): add DRBD-aware Talos node-upgrade runbook#16
Draft
Andrei Kvapil (kvaps) wants to merge 1 commit into
Draft
docs(cluster-upgrade): add DRBD-aware Talos node-upgrade runbook#16Andrei Kvapil (kvaps) wants to merge 1 commit into
Andrei Kvapil (kvaps) wants to merge 1 commit into
Conversation
The skill previously covered only the cozy-installer Helm upgrade; the OS layer (control-plane vs worker ordering, drain, waiting for DRBD resync between nodes) was undocumented, and a real cluster hit a VM-availability bug during that gap. - Add references/talos-node-upgrade.md: node-by-node Talos upgrade with the one-node-at-a-time / wait-for-UpToDate rule, storage pre-flight, and the auto-diskful exposure note. - Add known-failure #8: LINSTOR auto-diskful block-size mismatch that pauses VMs on DRBD 9.2.16 (setting new queue limits failed), with the virtctl-restart and auto-block-size mitigations and the DRBD 9.2.17 / Talos 1.13 fix path. - Wire both into SKILL.md (new section, red-flag row, references). Assisted-By: Claude Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Warning Gemini encountered an error creating the review. You can try again by commenting |
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
1 participant
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.
What
Adds a Talos / node OS upgrade runbook to the
cluster-upgradeskill anddocuments the LINSTOR
auto-diskfulblock-size failure that can pause VMs onDRBD 9.2.16.
references/talos-node-upgrade.md— node-by-node Talos upgrade: layerordering (Talos → Kubernetes → Cozystack), storage pre-flight, the
one-node-at-a-time / wait-for-
UpToDaterule, and the auto-diskful exposurenote.
known-failures.mdcozy-bump: SKILL.md backtick sequence breaks slash-command preprocessor #8 — the diskless(512)/diskful(4096) block-size mismatch:root cause (
queue_limits_commit_update()failing on DRBD 9.2.16 + kernel6.x), mitigations (
virtctl restart,auto-block-size=Falsefor newvolumes, replica placement), and the DRBD 9.2.17 / Talos 1.13 fix path.
SKILL.md— new "Node / Talos OS upgrades" section, a red-flag row, and thereference link.
Why
The skill covered only the
cozy-installerHelm upgrade. The OS layer —control-plane vs worker ordering, draining, and waiting for DRBD resync between
nodes — was undocumented, which is exactly where a production cluster hit a
VM-availability bug during an upgrade. This captures both the runbook and the
failure mode so the next operator has them.
Validation
tools/check-refs.shpasses (cross-references,--contextusage, no privatecluster names).