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

Self hosted koku for disconnected customer

XMLWordPrintable

    • Icon: Feature Feature
    • Resolution: Duplicate
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 1
    • False
    • Hide

      None

      Show
      None
    • False

      Hi cost management team,

      I am a Red Hat consultant currently working with a customer who is looking to set up some cost management "showback" and "chargeback" for various internal departments that use their baremetal OpenShift cluster. Due to security requirements, their cluster is fully disconnected from the internet and not able to upload data to the Red Hat Hybrid Cloud Console or Red Hat Insights. They are also not willing to manually upload data collected by the Cost Management Operator to the internet.

      We are looking for a way to do the following:

      • The ability to report costs based on CPU, Memory, Storage and GPU usage per namespace on a monthly basis
      • Fully self host the system that reports this data

      I was able to install the Cost Management Operator using this guide: https://docs.redhat.com/en/documentation/cost_management_service/1-latest/html/integrating_openshift_container_platform_data_into_cost_management/assembly-adding-openshift-container-platform-int#assembly-adding-a-restricted-network-int_adding-an-ocp-int
      I was also able to generate a csv using the operator and download it locally.

      Do you have any examples of a customer successfully self hosting a Koku deployment in order to consume + visualise this data?

      We may be able to come up with some bespoke way of parsing the Cost Management Operator output if this is not going to be possible but I would prefer not to "re-invent the wheel" on this one.

      Thanks,

      Jack

              Unassigned Unassigned
              jadolph@redhat.com Jack Adolph
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: