3 ms·

These are valid points. I’ve personally needed to do things like delete the StatefulSet, change volume size, update/change pvc, update StatefulSet, reapply. I

These are valid points. I’ve personally needed to do things like delete the StatefulSet, change volume size, update/change pvc, update StatefulSet, reapply. I just took it as a given and hadn’t thought much about the ergonomics. It’s really not that big of a deal and probably a ten minute process, tops. That said, OP makes a good point that mechanisms to handle this kind of stuff exist in CSI, so why not leverage / take advantage of that versus pissing in the wind (especially when you run into CRD that wants to undo the above work while you’re in the process)?

smarterclayton 4y ago
At the time we designed the StatefulSet, the resize behavior hadn’t been designed / finalized. Now that it has, it’s really a matter of someone having the time and patience to drive it though. I don’t know whether someone has sorted out all the design implications (like what happens if someone adds new resource requests, or what happens if a new resource request is rejected, and how that gets reported to the user), but it’s a small change that needs a fair amount of design thought, which tends to be hard to drive through.