It seems not all storageclass support this

Phani M:
Thanks @Basavraj Nilkanthe I’m able to resize the pvc with the standard sc

"spec": {
        "accessModes": [
            "ReadWriteOnce"
        ],
        "resources": {
            "requests": {
                "storage": "70Mi"
            }

Initially the pvc was created with 10Mi request and later able to resize to 70Mi

Malayamanas Panda:
if the PV size is 100 Mi and that PV is selected by a PVC, which claim is 10Mi, entire 100Mi is assigned to the PVC. 100Mi PV can not be used by any other PVC.

Malayamanas Panda:
Here, the question is NOT about PV, but PVC size expansion .

Malayamanas Panda:
I did a test, that PVC size can be increased but not be decreased .

Basavraj Nilkanthe:
yes shrinkage is not yet allowed

Basavraj Nilkanthe:
this feature is not yet enabled

Narendra Singh:
@Basavraj Nilkanthe for patching which command you have used. Is it edit or some other command. Please share the docs if any.

Basavraj Nilkanthe:
Yes it’s edit

Phani M:
I used the patch command shown like this and it worked fine.

k patch pvc myclaim -p '{"spec":{"resources":{"requests":{"storage":"75Mi" } } } }' --record=true

Here is the annotation being added

root@phani-dboard-2:~# k describe pvc myclaim
Name:          myclaim
Namespace:     default
StorageClass:  standard
Status:        Bound
Volume:        pv0003
Labels:        <none>
Annotations:   <http://kubernetes.io/change-cause|kubernetes.io/change-cause>: kubectl patch pvc myclaim --patch={"spec":{"resources":{"requests":{"storage":"2Gi" } } } } --record=true
               <http://pv.kubernetes.io/bind-completed|pv.kubernetes.io/bind-completed>: yes
               <http://pv.kubernetes.io/bound-by-controller|pv.kubernetes.io/bound-by-controller>: yes
Finalizers:    [<http://kubernetes.io/pvc-protection|kubernetes.io/pvc-protection>]
Capacity:      4Gi
Access Modes:  RWO
VolumeMode:    Filesystem
Used By:       &lt;none&gt;
Events:        &lt;none&gt;