Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ST] Node Pools role changes. Role change and scale down prevention if replicas present. #9693

Merged
merged 2 commits into from
Feb 23, 2024

Conversation

henryZrncik
Copy link
Contributor

@henryZrncik henryZrncik commented Feb 15, 2024

Type of change

  • Enhancement

Description

addition of checks when preventing Scale down or role change (removal of broker role) in case given nodes (brokers) still contains replicas.

addition of new test (which can be in a future further extended), to cover role changes. As currently the only role transition fully supported is from Mixed role to Controller only, test contains only that. I did not incorporated it into the other tests as this is so far kraft specific and would create a mess of resources creation in other node pools tests.

also test testCruiseControlDuringBrokerScaleUpAndDown is enabled and fixed (to work in kraft) as well, this was done instead of adding CC into Kafka Node Pool specific test as there would be too big overlap. some checks there were removed as they were redundant, only significant parts there are that we create sepate roles instead of calling NodePoolsConverter.convertNodePoolsIfNeeded as this test does not need to run in mixed mode. also there is annotation for specific Ids for controllers in order to not need to introduce additional logic into Rebalancing and ids which would be changed due to 3 extra (controllers) Ids taken.

@henryZrncik henryZrncik self-assigned this Feb 15, 2024
@henryZrncik henryZrncik added this to the 0.40.0 milestone Feb 15, 2024
@henryZrncik
Copy link
Contributor Author

do not merge before testNodePoolsRolesChanging

@see-quick
Copy link
Member

/azp run regression

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@im-konge im-konge left a comment

Choose a reason for hiding this comment

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

Few nits, mostly things that changed after my latest PR. Anyway thanks for the PR :)

Copy link
Member

@im-konge im-konge left a comment

Choose a reason for hiding this comment

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

LGTM, thanks :)

Copy link
Member

@see-quick see-quick left a comment

Choose a reason for hiding this comment

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

LGTM, just one thing to consider but nothing, which is blocker to merge this PR

Signed-off-by: hzrncik <[email protected]>
@see-quick
Copy link
Member

/azp list

@see-quick
Copy link
Member

/azp run kraft-regression

Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@see-quick see-quick added the ready for merge Label for PRs which are ready for merge label Feb 23, 2024
@see-quick see-quick merged commit c58e67c into strimzi:main Feb 23, 2024
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for merge Label for PRs which are ready for merge System tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants