1. In the OpenShift Container Platform web console, click on the Workloads > Secrets tab.
2. In the Secrets window, select Project:costmanagement-metrics-operator from the dropdown.
3. Click the Create > Key/Value Secret selection.

4. In the Create Key/Value Secret window enter the following information to create a new secret that contains a username key and a password key and a value for each key.

   1. Enter a name for your secret in the Secret Name field.

      basic-auth-secret

   2. In the Key field, enter username.

      username

   3. In the Value field for the key username, enter the actual username for your authorized Red Hat Hybrid Cloud Console user account.

      Value for username key

      your_red_hat_username

   4. Click the Add Key/Value link to add the required password key name and value.

   5. In the Key field, enter password.

      password

   6. In the Value field for the key password, enter the actual password for your authorized Red Hat Hybrid Cloud Console user account.

      Value for password key

      your_red_hat_password

   7. Click the Create button to complete the creation of your basic authorization secret.

   8. After you click the Create button, you can verify the key/value details for the secret.

      Note

      Do not add the secret to the workload.

Procedure

1. Click on the Operators > Installed Operators tab.
2. Locate the row that contains Cost Management Metrics Operator and click on the Cost Management Metrics Operator link that is under the Provided APIs heading.

3. When the CostManagementMetricsConfig window appears, click on the configuration file listed in the Name column.

   The default name is costmanagementmetricscfg-sample.

4. When the costmanagementmetricscfg-sample window appears, click in the YAML tab to open an edit and view window.

5. Locate the following lines in the YAML view.

     authentication:
       type: token

6. Change type: token to type: basic.

7. Insert a new line for secret_name. Enter the value for secret_name, which is the name you previously created.

   Example

     authentication:
       secret_name: basic-auth-secret
       type: basic

8. Click the Save button. A confirmation message appears.

Procedure

1. Complete the following OpenShift Container Platform procedure to create a local mirror of the costmanagement-metrics-operator: Using Operator Lifecycle Manager on restricted networks.

   Note

   The costmanagement-metrics-operator is found in the redhat-operators catalog in the registry.redhat.io/redhat/redhat-operator-index:v4.11 index.

   Red Hat recommends pruning unwanted objects from the index before pushing to the mirrored registry. Make sure you keep the costmanagement-metrics-operator package.

2. Log in to the OpenShift Container Platform web console and click Operators > OperatorHub.
3. Search for and locate Cost Management Metrics Operator.
4. Click the Cost Management Metrics Operator tile.
5. When the Install Operator window appears, you must select the costmanagement-metrics-operator namespace for installation. If the namespace does not yet exist, it is created for you.
6. Click Install.

Procedure

1. From the OpenShift Container Platform web console, select Operators > Installed Operators > costmanagement-metrics-operator > CostManagementMetricsConfig > Create Instance.

2. Specify the desired storage. If not specified, the operator will create a default persistent volume claim called costmanagement-metrics-operator-data with 10Gi of storage.

   Note

   To configure the costmanagement-metrics-operator to use or create a different PVC, update the volume_claim_template configuration in YAML view.

3. Select YAML view.

4. Specify the maximum number of reports to store using max_reports_to_store, and time between report generation in minutes using upload_cycle.

       packaging:
         max_reports_to_store: 30
         max_size_MB: 100

       upload:
         upload_cycle: 360

   Important

   The costmanagement-metrics-operator creates one report every 360 minutes by default. Therefore, the default value of 30 reports and 360 minutes gives you 7.5 days of reports.

   Any report generated after the total number specified will replace the oldest report in storage. Download generated reports from your PVC before they are lost.

5. Set upload_toggle to false.

       upload:
         upload_cycle: 360
         upload_toggle: false

6. Replace the configuration in the source section with empty brackets.

       source: {}

7. Replace the configuration in the authentication section with empty brackets.

       authentication: {}

8. Click Create.

Verification steps

1. Select the CostManagementMetricsConfig you created.
2. Select YAML view.

3. Verify that a report has been created in the packaging section.

       packaging:
         last_successful_packaging_time: `current date and time`
         max_reports_to_store: 30
         max_size_MB: 100
         number_of_reports_stored: 1
         packaged_files:
           - >-
               /tmp/costmanagement-metrics-operator-reports/upload/YYYYMMDDTHHMMSS-cost-mgmt.tar.gz

   Note

   costmanagement-metrics-operator will generate an initial report after it is configured. Generated reports will be listed under packaged_files.

Procedure

1. Create the following pod with claimName matching the PVC containing the report data:

   kind: Pod
   apiVersion: v1
   metadata:
     name: volume-shell
     namespace: costmanagement-metrics-operator
   spec:
     volumes:
     - name: costmanagement-metrics-operator-reports
       persistentVolumeClaim:
         claimName: costmanagement-metrics-operator-data
     containers:
     - name: volume-shell
       image: busybox
       command: ['sleep', '3600']
       volumeMounts:
       - name: costmanagement-metrics-operator-reports
         mountPath: /tmp/costmanagement-metrics-operator-reports

2. Use rsync to copy all of the files from the PVC to a local folder.

   $ oc rsync volume-shell:/tmp/costmanagement-metrics-operator-reports/upload local/path/to/save/folder

3. Confirm that the files have been copied.

4. Connect to the pod and delete the contents of the upload folder.

   $ oc rsh volume-shell
   $ rm /tmp/costmanagement-metrics-operator-reports/upload/*

5. (Optional) Delete the pod that was used to connect to the PVC.

   $ oc delete -f volume-shell.yaml

Verification steps

1. From cost management, click OpenShift.
2. Verify you have OpenShift usage data for your cluster on the OpenShift details page.