I have a persistent volume (PV) and persistent volume claim (PVC) which got bound as well. Initially, the storage capacity was 2Gi for the PV and the requested storage from PVC was 1Gi. I then edit the existing bound PV and increased the storage to 5Gi with the record flag as --record.

vagrant@mykubemaster:~/my-k8s$ kubectl get pv
NAME    CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM         STORAGECLASS   REASON   AGE
my-pv   2Gi        RWO            Retain           Bound    test/my-pvc                           106s

vagrant@mykubemaster:~/my-k8s$ kubectl edit pv my-pv --record

persistentvolume/my-pv edited
vagrant@mykubemaster:~/my-k8s$ kubectl get pv
NAME    CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM         STORAGECLASS   REASON   AGE
my-pv   5Gi        RWO            Retain           Bound    test/my-pvc                           2m37s

Now my question is if there is any way by which I can confirm that this --record flag have certainly recorded this storage change (edit PV) in history.

With deployments, it is easy to check with the kubectl rollout history <deployment name> but I'm not sure how to check this with other objects like PV.

Please assist. thanks