Verify the PVC status: Use kubectl describe pvc <pvc-name> to verify that the PVC status is "Bound" and that the new size is reflected in the output.
Note that resizing a PVC will trigger a resize operation on the underlying storage volume, which may take some time to complete. Also, not all storage providers support dynamic resizing, so be sure to check your provider's documentation before attempting to resize a PVC.
Name: artifactory-volume-jfrt-artifactory-0 Namespace: vigneshs StorageClass: standard Status: Bound Volume: pvc-f555ab44-f07b-41dd-a1dd-b39c6c8dce4e Labels: app=artifactory release=jfrt role=artifactory Annotations: pv.kubernetes.io/bind-completed: yes pv.kubernetes.io/bound-by-controller: yes volume.beta.kubernetes.io/storage-provisioner: pd.csi.storage.gke.io volume.kubernetes.io/storage-provisioner: pd.csi.storage.gke.io volume.kubernetes.io/storage-resizer: pd.csi.storage.gke.io Finalizers: [kubernetes.io/pvc-protection] Capacity: 30Gi Access Modes: RWO VolumeMode: Filesystem Used By: jfrt-artifactory-0 Events: <none>
Note that resizing a PVC will trigger a resize operation on the underlying storage volume, which may take some time to complete. Also, not all storage providers support dynamic resizing, so be sure to check your provider's documentation before attempting to resize a PVC.