[v/25.3] manage/k8s: document decommission timing (--decommission-wait-interval)#1763
Conversation
…t-interval, RequeueAfter) Backport of #1761 to v/25.3. Adds the "Tune automatic decommission timing" section (--decommission-wait-interval for the Operator; decommissionRequeueTimeout and decommissionAfter for the Helm sidecar), a TIP cross-reference, and the shell-correct --set "additionalCmdFlags={...}" quoting. The Operator-example rewrite from #1761 is main-only and intentionally omitted: v/25.3's Operator example uses the version-appropriate brokerDecommissioner sidecar, so backporting that paragraph/callout would contradict the example. Co-Authored-By: Claude Opus 4.8 (1M context) <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 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 |
The new Netlify build image (noble-new-builds) defaults to node 22 / npm 10.9.3 when no version is pinned, which fails `npm install` on this branch with `ERR_INVALID_ARG_TYPE: The "from" argument must be of type string. Received undefined`. This branch's deps install cleanly on node 20 (the version pinned in .github/workflows/test-docs.yml, where the Antora build passes) but not on node 22. This branch had no netlify.toml, so add a minimal one pinning node 20 and matching main's NODE_OPTIONS. Restores the broken Netlify preview build; no content changes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
micheleRP
left a comment
There was a problem hiding this comment.
Backport review — LGTM
Verified this backport of #1761 against `v/25.3`; it's technically correct and version-appropriate:
- `--decommission-wait-interval` is a real operator flag (`redpanda-operator` `operator/cmd/run/run.go`, default `8s`), valid for the operator version pinned on this branch (`v2.3.8-24.3.6`). ✓
- Cross-references resolve on `v/25.3`: `<>`, `<>` (`[[Automated]]` present), and the `reference:{cluster,tunable}-properties.adoc#...` xrefs via the existing `page-aliases` on `properties/cluster-properties.adoc`. ✓
- Correctly omits the main-only Operator-example rewrite, since `v/25.3`'s Operator example uses the `brokerDecommissioner` sidecar. ✓
- Shell-quoting fix (`--set "additionalCmdFlags={--additional-controllers=decommission}"`) is correct.
One note (no action needed): the second commit bundles a `netlify.toml` CI fix (`NODE_VERSION = "20"`) to unblock the preview build on this branch — unrelated to the content but justified and self-contained.
Backport of #1761 to v/25.3.
Adds the "Tune automatic decommission timing" section to the Kubernetes decommission page:
--decommission-wait-interval(Operator, viaadditionalCmdFlags) — the Decommission controller's requeue interval (RequeueAfter).decommissionRequeueTimeout/decommissionAfter(Helm sidecar).--set "additionalCmdFlags={...}"quoting, and guidance for adjusting the intervals.Backport note
The Operator-example rewrite from #1761 (the "do not add
sideCars.brokerDecommissionerhere" paragraph +<1>callout) is main-only and intentionally omitted here: v/25.3's Operator example uses the version-appropriatebrokerDecommissionersidecar, so backporting that paragraph would contradict the example on this branch.Verified that all cross-references resolve on v/25.3:
<<decommission-timing>>,<<Automated>>, andreference:{cluster,tunable}-properties.adoc#...(the latter via the existingproperties/cluster-properties.adocpage-aliases, already used elsewhere on this branch).🤖 Generated with Claude Code