-
Task
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
-
5
-
False
-
False
Summary
It appears as if `kube_persistentvolume_info` now has a field `ebs_volume_id` that has the underlying `vol-` resource id for the AWS EBS volume behind a volume. If we can collect this we could enhance our OCP on AWS story by directly matching storage costs to the cluster.
Docs moved to here: https://github.com/kubernetes/kube-state-metrics/blob/main/docs/metrics/storage/persistentvolume-metrics.md
UPDATE:
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.
- is cloned by
-
COST-4865 Operator: Start Collecting GCP volume identifier
- Closed