Remove particular pod instead of last broker (not on statefulset)

[kshitijmjoshi]

This question is related to #3527

We are on Strimzi latest (0.33.2) with Kafka version 3.4.0.

We have brokers 0 & 1 on gp2 volumes which we'd like to upgrade to gp3 (change the storage class) without downtime.

Since storageClass of PVs cannot be changed once they are created, I was planning to

1. move all the topics to broker 3,4 (already backed by gp3 volumes).
2. delete pods 0 and 1 and their PVCs.
3. recreate brokers 0 & 1 with new PVCs.

Since Strimzi no longer uses statefulSet, can a particular pod be taken down now instead of the last pod?

If not, is there a recommended method to change the storage class of particular pods? Thanks!

[scholzj]

If you use JBOD storage ... why don't you add new disk, move the data there and remove the old disk?

[kshitijmjoshi]

This worked perfectly fine! No issues. Thanks for the directions.
Is there a recommendation for the zookeeper pods as well?

[scholzj]

How many ZooKeeper nodes you have? You can try something similar I guess ->

• Make sure you have 3 or 5 ZooKeeper nodes
• Scale down the operator and delete the nodes one by one with the same process as for Kafka

ZooKeeper nodes are all active. So you cannot reassign the data. But you need majority of them to be online, so if you take it one by one, it should not cause availability issue. Just make sure you leave enough time between the individual nodes for them to resync the data.

(Again, not tested by myself recently, so you would need to test this)

[kshitijmjoshi]

Thanks! We have 3 nodes. I'll try it and post an update here.

[kshitijmjoshi]

Worked fine with no downtime. Thanks for the guidance!

[scholzj]

Great, glad it worked. Thanks for confirming.