Uploaded image for project: 'Cost Management'
  1. Cost Management
  2. COST-2297

Operator: Start Collecting AWS volume identifier

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Duplicate
    • Icon: Major Major
    • None
    • None
    • Operators
    • 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:

      https://docs.openshift.com/container-platform/4.15/storage/persistent_storage/persistent-storage-aws.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.

       

        1. kube_persistentvolume_info-aws.json
          19 kB
          Chris Hambridge
        2. kube_persistentvolume_info-azure.json
          1 kB
          Chris Hambridge
        3. kube_persistentvolume_info-gcp.json
          1 kB
          Chris Hambridge

              Unassigned Unassigned
              kholdawa@redhat.com Kevan Holdaway
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: