Summary

It appears as if `kube_persistentvolume_info` now has a field `gce_persistent_disk_name` that has the underlying persistent disk name for the GCP's Persistent Disk. If we can collect this we could enhance our OCP on GCP story by directly matching storage costs to the cluster.

See: https://github.com/kubernetes/kube-state-metrics/blob/main/docs/metrics/storage/persistentvolume-metrics.md

UPDATE:

https://docs.openshift.com/container-platform/4.15/storage/persistent_storage/persistent-storage-gce.html

The plug in that is providing unique identifier for the volume is being deprecated in favor of moving to the equivalent Container Storage Interface (CSI) driver. We added a volume using the new CSI driver in our demo account, and discovered that for AWS the csi_volume_handle metric was equivalent to the ebs_volume_id. We believe the same to be true for the gce_persistent_disk_name; however, we confirm using clusterbot.