<p>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 <code>--record</code>.</p>
<pre><code>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
</code></pre>
<p>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.</p>
<p>With deployments, it is easy to check with the <code>kubectl rollout history &lt;deployment name&gt;</code> but I'm not sure how to check this with other objects like PV.</p>
<p>Please assist. thanks</p>

vinod827
<p>As mentioned in <a href="https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands" rel="nofollow noreferrer"><code>kubectl</code> references docs</a>:</p>
<pre><code>Record current kubectl command in the resource annotation. If set to false, do not record the command. If set to true, record the command. If not set, default to updating the existing annotation value only if one already exists.
</code></pre>
<p>You can run <code>kubectl get pv my-pv -o yaml</code> and you should see that <code>kubernetes.io/change-cause</code> was updated with the command that you ran. In your case, it will be <code>kubectl edit pv my-pv --record</code>.</p>
<p>The <a href="https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#rollout" rel="nofollow noreferrer"><code>rollout</code></a> command that you mentioned (including <code>rollout history</code>) works only with the following resources:</p>
<ul>
<li>deployments</li>
<li>daemonsets</li>
<li>statefulsets</li>
</ul>
