Skip to content

[v/25.3] manage/k8s: document decommission timing (--decommission-wait-interval)#1763

Merged
david-yu merged 2 commits into
v/25.3from
dyu/backport-1761-decommission-v25.3
Jun 24, 2026
Merged

[v/25.3] manage/k8s: document decommission timing (--decommission-wait-interval)#1763
david-yu merged 2 commits into
v/25.3from
dyu/backport-1761-decommission-v25.3

Conversation

@david-yu

Copy link
Copy Markdown
Contributor

Backport of #1761 to v/25.3.

Adds the "Tune automatic decommission timing" section to the Kubernetes decommission page:

  • --decommission-wait-interval (Operator, via additionalCmdFlags) — the Decommission controller's requeue interval (RequeueAfter).
  • decommissionRequeueTimeout / decommissionAfter (Helm sidecar).
  • A TIP cross-reference from the Operator install step, the shell-correct --set "additionalCmdFlags={...}" quoting, and guidance for adjusting the intervals.

Backport note

The Operator-example rewrite from #1761 (the "do not add sideCars.brokerDecommissioner here" paragraph + <1> callout) is main-only and intentionally omitted here: v/25.3's Operator example uses the version-appropriate brokerDecommissioner sidecar, so backporting that paragraph would contradict the example on this branch.

Verified that all cross-references resolve on v/25.3: <<decommission-timing>>, <<Automated>>, and reference:{cluster,tunable}-properties.adoc#... (the latter via the existing properties/cluster-properties.adoc page-aliases, already used elsewhere on this branch).

🤖 Generated with Claude Code

…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>
@netlify

netlify Bot commented Jun 24, 2026

Copy link
Copy Markdown

Deploy Preview for redpanda-docs-preview ready!

Name Link
🔨 Latest commit d58d729
🔍 Latest deploy log https://app.netlify.com/projects/redpanda-docs-preview/deploys/6a3c1b565816a30008d882da
😎 Deploy Preview https://deploy-preview-1763--redpanda-docs-preview.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai

coderabbitai Bot commented Jun 24, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 34be689a-10a8-4a97-bef6-f3a1dc1d44f6

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dyu/backport-1761-decommission-v25.3

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

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 micheleRP left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants