acceptance: Change decommission node pruning #1203
Merged
Conversation
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
In the current decommission test, the K3D node is removed, but for some unknown reason more Kubernetes nodes than the removed can become unhealthy. When the step, that removes unhealthy nodes, deletes two Kubernetes nodes, it can result in two Redpanda nodes going offline. The decommission test runs a three-node Redpanda cluster, so the decommission controller often cannot complete the decommission in time.
RafalKorepta
requested review from
andrewstucki,
chrisseto and
gene-redpanda
as code owners
andrewstucki
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In the current decommission test, the K3D node is removed, but for some unknown reason more Kubernetes nodes than the removed can become unhealthy. When the step, that removes unhealthy nodes, deletes two Kubernetes nodes, it can result in two Redpanda nodes going offline. The decommission test runs a three-node Redpanda cluster, so the decommission controller often cannot complete the decommission in time.