DOC-2237: correct decommission + maintenance mode guidance (v/25.2 backport)#1737
Open
Feediver1 wants to merge 5 commits into
Open
DOC-2237: correct decommission + maintenance mode guidance (v/25.2 backport)#1737Feediver1 wants to merge 5 commits into
Feediver1 wants to merge 5 commits into
Conversation
The CAUTION on the Maintenance Mode page incorrectly stated that a broker cannot be decommissioned while in maintenance mode. This was true only in 22.x and older. From 24.1.15 / 24.2.1 onward, decommission gracefully drains partition leadership on its own, so maintenance mode beforehand is optional. - modules/manage/pages/node-management.adoc: replace CAUTION with a NOTE clarifying maintenance mode beforehand is optional. - modules/upgrade/partials/rolling-upgrades/enable-maintenance-mode.adoc: drop "decommissioning or" from the rolling-upgrade/restart trouble- shooting notes so they no longer imply maintenance mode blocks decommissioning. - modules/manage/pages/cluster-maintenance/decommission-brokers.adoc and modules/manage/pages/kubernetes/k-decommission-brokers.adoc: add a matching positive-framing NOTE on the decommission side. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI 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)
Comment |
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
kbatuigas
approved these changes
Jun 10, 2026
Prevents 'Duplicate nav' fatal during Antora build. The local worktree (.) and the remote v/* glob were both supplying the same nav file for the current version. Other version branches (v/25.3, v/24.x, v/23.3) already self-exclude; this aligns v/25.2 with them.
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.
Backports DOC-2237 to
v/25.2. The Maintenance Mode page incorrectly stated that a broker cannot be decommissioned while in maintenance mode; from 24.1.15 / 24.2.1 onward, decommission gracefully drains partition leadership on its own.Scope (one playbook fix included)
In addition to the doc-content changes, this PR also adds a one-line self-exclusion to
local-antora-playbook.ymlso the Antora build doesn't hit a "Duplicate nav" fatal. The playbook onv/25.2was missing'!v/25.2'from the remote docs source — every other version branch (v/25.3, v/24.x, v/23.3) already has its own self-exclusion. This change aligns v/25.2 with them and is needed for the PR's own build to succeed.Companion PR on
main: #1735Preview pages
🤖 Generated with Claude Code