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.

Sign up for GitHub

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

Jump to bottom

[ST] KafkaNodePools Roll only broker role due to broker only config change #9540

Merged
merged 1 commit into from
Jan 19, 2024
Merged

[ST] KafkaNodePools Roll only broker role due to broker only config change #9540

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
18 changes: 15 additions & 3 deletions systemtest/src/test/java/io/strimzi/systemtest/rollingupdate/KafkaRollerST.java
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -343,9 +343,11 @@ void testKafkaPodPendingDueToRack(ExtensionContext extensionContext) {
* 3. - Take snapshots of the broker and controller pods for later comparison.
* 4. - Update a specific Kafka configuration that affects only controller nodes and verify the rolling update behavior.
* - Ensure that only controller nodes undergo a rolling update, while broker nodes remain unaffected.
* 5. - Introduce a change in the controller node pool, such as modifying pod affinity.
* 5. - Update a specific Kafka configuration that affects only broker nodes and verify the rolling update behavior.
* - Ensure that only broker nodes undergo a rolling update, while controller node remain unaffected.
* 6. - Introduce a change in the controller node pool, such as modifying pod affinity.
* - Observe and ensure that this change triggers another rolling update for the controller nodes.
* 6. - Verify the rolling updates of controller nodes by comparing the snapshots taken before and after each configuration change.
* 7. - Verify the rolling updates of controller nodes by comparing the snapshots taken before and after each configuration change.
*
* @usecase
* - kafka-controller-node-rolling-update
Expand All @@ -354,7 +356,7 @@ void testKafkaPodPendingDueToRack(ExtensionContext extensionContext) {
* - kafka-node-pool-management
*/
@ParallelNamespaceTest
void testKafkaRollingUpdatesOfControllerNodes(final ExtensionContext extensionContext) {
void testKafkaRollingUpdatesOfSingleRoleNodePools(final ExtensionContext extensionContext) {
assumeTrue(Environment.isKRaftModeEnabled());
assumeFalse(Environment.isOlmInstall() || Environment.isHelmInstall());

Expand Down Expand Up @@ -389,6 +391,16 @@ void testKafkaRollingUpdatesOfControllerNodes(final ExtensionContext extensionCo
// broker-role nodes does not roll
RollingUpdateUtils.waitForNoRollingUpdate(testStorage.getNamespaceName(), brokerPoolSelector, brokerPoolPodsSnapshot);

// change Broker-only configuration inside shared Kafka configuration between KafkaNodePools and see that only broker pods rolls
KafkaUtils.updateSpecificConfiguration(testStorage.getNamespaceName(), testStorage.getClusterName(), "initial.broker.registration.timeout.ms", 33500);

// only broker-role nodes rolls
brokerPoolPodsSnapshot = RollingUpdateUtils.waitTillComponentHasRolledAndPodsReady(testStorage.getNamespaceName(),
brokerPoolSelector, brokerPoolReplicas, brokerPoolPodsSnapshot);

// controller-role nodes does not roll
RollingUpdateUtils.waitForNoRollingUpdate(testStorage.getNamespaceName(), controllerPoolSelector, controllerPoolPodsSnapshot);

// 2nd Rolling update triggered by PodAffinity

// Modify pod affinity settings for the controller node pool
Expand Down