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

Update resource matching (GCP)

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • None

      GCP

      The volume_id is located in the resource_global_name field and follows the following syntax:

      //compute.googleapis.com/projects/<project-id>/zones/<zone>/disk/<disk-id>

      There will be a new csi_volume_handle key added to the persistent volume labels to use for resource matching logic.

      We want to update the match_openshift_resources_and_labels function to handle this new resource matching.

      • Updating here prevents us from having to worry about the key being enabled
      • It also allows us to bypass the key being removed because it is disabled during the trino to postgresql transition

              Unassigned Unassigned
              myersco Cody Myers
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: