about external-resizer

[lijhnihaoa]

I want to add the volume expansion function on this basis, but after adding the v1.4.0 version of external-resizer, I found that
updatedPVC, err := ctrl.patchClaim(pvc, newPVC, true /* addResourceVersionCheck */) This function reports an error, the reason for the error Error syncing PVC: marking pvc "kube-csi/volume-pvc" as resizing failed: can' t patch status of PVC kube-csi/volume-pvc with persistentvolumeclaims "volume-pvc" is forbidden, I judge that the version may be too high and not suitable, may I ask is this the reason?

[lijhnihaoa]

updatedClaim, updateErr := ctrl.kubeClient.CoreV1().PersistentVolumeClaims(oldPVC.Namespace). Patch(context.TODO(), oldPVC.Name, types.StrategicMergePatchType, patchBytes, metav1.PatchOptions{}, "status") if updateErr != nil { return oldPVC, fmt.Errorf("can't patch status of PVC %s with %v", util.PVCKey(oldPVC), updateErr) }

[lijhnihaoa]

the reason for the error Error syncing PVC: marking pvc "kube-csi/volume-pvc" as resizing failed: can't patch status of PVC kube-csi/volume-pvc with persistentvolumeclaims "volume-pvc" is forbidden: User "system:serviceaccount:kube-csi:spdkcsi-controller-sa" cannot patch resource "persistentvolumeclaims/status" in API group "" in the namespace "kube-csi"

[cyb70289]

Not familiar with external-resize buut this looks like rbac configuration issue. We might need additional cluster roles such as persistentvolumeclaims/status.
You can compare below code with external-resizer document for possible missing roles.
https://github.com/spdk/spdk-csi/blob/master/deploy/kubernetes/controller-rbac.yaml

[lijhnihaoa]

You reminded me, thanks for giving me direction to think.

[cyb70289]

@lijhnihaoa It will be great if you want to upstream new features to spdk-csi project.