docs: per-broker restart probes for operator rolling restarts (26.2)#1826
docs: per-broker restart probes for operator rolling restarts (26.2)#1826david-yu wants to merge 2 commits into
Conversation
…restarts Add 'How the Redpanda Operator gates each restart' to the Kubernetes rolling-restart page (operator PR #1547): the pre-restart probe blocks a broker's restart while it would lose acks=1 data, make partitions unavailable, or stall acks=all produce; the post-restart probe holds the next restart until the recovering broker reports 100% of its in-sync-replica load reclaimed, since pod readiness alone doesn't prove catch-up. One broker per pass, Redpanda 25.1+ for the probe endpoints, cluster-wide health fallback on older versions. Adds the v26.2.x what's-new entry. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
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 Plus 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 |
….2.1 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Documents the per-broker pre/post-restart probes that gate operator-driven rolling restarts (redpanda-operator#1547, merged 2026-06-25, ships in operator v26.2.x).
Changes
How the Redpanda Operator gates each restartunder "What happens during a rolling restart" onmanage:kubernetes/k-rolling-restart.adoc:GET /v1/broker/pre_restart_probe): the restart is delayed while it would loseacks=1-acknowledged data, make partitions unavailable, or blockacks=allproduce; replication-factor-1 partitions don't block (no redundancy to preserve — cross-linked to the existing RF-1 guidance in the procedure)GET /v1/broker/post_restart_probe): the next restart is held until the recovering broker reports 100% of its in-sync-replica load reclaimed, because Pod readiness can pass while the broker is still replaying partition stateSafer rolling restarts with per-broker health probesentry under Redpanda Operator v26.2.x inget-started:release-notes/operator.adoc.Verification
Content follows the eng PR's probe contract and was cross-checked against operator
main:internal/probes/broker.go(risk-category interpretation,load_reclaimed_pc >= 100threshold, 404 fallbacks) andinternal/lifecycle/client.go(operator-managed StatefulSets use theOnDeleteupdate strategy, so the operator's gated roll loop performs the restarts). The eng PR's EKS E2E (6 brokers, sustained rolls under load) recorded 88 post-restart deferrals and 32 pre-restart blocks with zero acks=1 loss.Note: this PR inserts a section under the v26.2.x what's-new heading, as do open PRs #1808 and #1825 — whichever merges later needs a trivial conflict resolution (the entries just stack).
Preview pages
🤖 Generated with Claude Code