Can I expand storage capacity without restarting the service?

[lyd100822]

Can I expand storage capacity without restarting the service? Because each storage expansion requires a rolling restart of the Kafka service, but directly expanding the capacity of the virtual machine can

[scholzj]

That depends on your infrastrcuture.

[lyd100822]

The specific operation steps are kubectl edit pvc pvc-name. Then change the storage size from 50G to 100G, and the storage will automatically expand. However, this violates the operator's management method and the Kafka service will not restart. If the storage size is changed from 50G to 100G through the YAML file, the service will be restarted. So, is there any other way to consult?

[scholzj]

Yes. Do not edit the PVCs as I said before. Do it through the Strimzi custom resource.

[lyd100822]

Editing and configuring custom resources through Strimzi will restart the service after modification. I just want to know whether it is possible to expand storage without restarting the service. You said before that it depends on the infrastructure. What is the solution? I want to know the following.

[scholzj]

Strimzi does restart any pods only when it is requested by the storage through the FileSystemResizePending condition. (through it is badly defined in Kubernetes, so it is not completely clear what it really indicates).

In any case, there is only one solution to it - resize it through the Strimzi CRs. Resizing should be rare enough event to make the rolling update acceptable.

[scholzj]

There is also #11279 to make it confiurable whether Strimzi should react to the FileSystemResizePending or not. In case your storage uses the condition but does not need restart. But nobody wrote the proposal for it and implemented it so far (hint: this is your chance 😉).