Skip to content

Instantly share code, notes, and snippets.

@myersCody
Last active June 28, 2024 14:53
Show Gist options
  • Save myersCody/b300fea8db309e55d50a7bf020a8e4b8 to your computer and use it in GitHub Desktop.
Save myersCody/b300fea8db309e55d50a7bf020a8e4b8 to your computer and use it in GitHub Desktop.

What's New?

Koku/Cost Management is now able to better report and distribute OpenShift storage costs, especially when running OpenShift on Azure. Enhancements for AWS, GCP and on-premise will follow.

Customers utilizing the Azure Disk CSI Driver storage class to dynamically provision persistent volumes, in conjunction with the latest release of the cost-management-metrics-operator, will now see improved correlation of Azure disk costs to OpenShift projects within the Azure filtered by OpenShift view. The latest operator enables us to collect the unique identifier for disks created by the CSI driver during the creation of persistent volumes.

For customers not using the latest operator, the previous method of matching persistent volume names to Azure disk resource identifiers will still be in use. However, this method can result in uncorrelated costs. We highly recommend adopting the new approach for optimal cost visibility.

Additionally, we've made significant improvements in assigning Azure disk costs to OpenShift projects. Through our extended efforts, we now map the capacity of Azure disks to the product name. This allows us to assign a portion of the disk cost based on the requested persistent volume capacity. The cost allocation is calculated using the following equation:

(Persistent volume capacity / Disk Capacity) * Cost of the Disk

The remaining unallocated portion of the disk cost has now been added under a new project called Storage unattributed. This project will now also include the cost of persistent volumes that have no persistent volume claims.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment