When attempting to upgrade/update/modify workloads with storage attached with rolling updates, the new pod can never initialize because the original won’t relinquish the claim. I some cases it is simple to just change the upgrade policy, but in other cases it is not so simple, such as with Apps “Launched” from within the ui.
For instance you get a bunch of Apps working and running for a few days with storage provisioned with Longhorn then you realize your cluster is getting a bit messy and you want to go and reorganize and change some of the projects and namespaces. The only way to do that is to delete all the storage?
Otherwise they seem to sit forever attempting to attach storage that their antecedents are holding in a death grip.