Restart the correct Pod when resizing PVCs #10396
Merged
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.
Type of change
Description
When resizing the PVCs, we might need to restart some of the Pods for the resizing to complete (file system expansion). But we might miss the right pod because the code currently does not work with node pools and expects that all Kafka pods will be named
<cluster-name>-kafka-<index>
.This PR addresses it and makes sure that the logic uses the correct name of the Pod depending on the node pool. That way it now works when using node pools or KRaft.
Checklist