During the DKP 1.x upgrade process, it is possible the Kommander Addon can get stuck in an 'upgrading' state as shown in https://support.d2iq.com/hc/en-us/articles/4409480536212-Why-does-Kommander-is-stuck-as-outdated-after-deploying-Konvoy-addons
A sample error message would contain:
only dynamically provisioned pvc can be resized and the storageclass that provisions the pvc must support resize
The related issue to this can be found in https://github.com/kubecost/cost-analyzer-helm-chart/issues/507 and as a known issue listed in https://docs.d2iq.com/dkp/kommander/1.4/release-notes/1.4.1/#known-issues where "the (Kommander 1.4.1) Kubecost cost analyzer requests a PVC of size 0.2Gi by default. This can cause issues with provisioners requiring a minimum storage size of 1Gi."
In the event that it is not possible to uninstall and reinstall kommander for any reason, there are two possible workarounds to resolve this issue:
- One is to delete the PV and retry the upgrade. This would create a new PV with the size defined in the PVC as introduced in Kommander 1.4.1.
- Another would be to check the original PVC size prior to the upgrade and modify the Kommander chart values for kubecost to match the size
- name: kommander enabled: true values: | kubecost: cost-analyzer: persistentVolume: size: 32Gi # whatever the original PVC size was, to avoid resizes
Further reading on this can be found in https://github.com/kubecost/docs/blob/master/storage.md