Skip to content

[release/v25.3.x] operator: settle each scale-down step before decommissioning the next (#1998) - #2022

Closed
github-actions[bot] wants to merge 1 commit into
release/v25.3.xfrom
backport/release/v25.3.x/pr-1998
Closed

github-actions[bot] wants to merge 1 commit into
release/v25.3.xfrom
backport/release/v25.3.x/pr-1998

Conversation

@github-actions

Copy link
Copy Markdown

Backport

This will backport the following commits from main to release/v25.3.x:

Questions ?

Please refer to the Backport tool documentation

…#1998)

Lowering statefulset.replicas by more than one broker deleted several
broker Pods at once, and only the first was decommissioned. Since
1743490, reconcilePools no longer aborts the chain while CheckScale is
false, so reconcileDecommission ran mid-scale. The previous step's
terminating Pod was still LastPod, and its decommissioned broker looked
already removed, so each pass patched away another broker without
decommissioning it. Partitions with a majority on those brokers lost
quorum.

Fixes K8S-955.

(cherry picked from commit fde0a00)

# Conflicts:
#	operator/internal/controller/redpanda/multicluster_controller.go
#	operator/internal/controller/redpanda/redpanda_controller_test.go
@secpanda

secpanda commented Oct 27, 2026 •

Copy link
Copy Markdown

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues
✅ Licenses 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@andrewstucki

Copy link
Copy Markdown
Contributor

backport unnecessary, the break only landed in 26.2.x

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants