You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using a custom pricing model, GPU prices can be assigned to __idle__ costs, even though the GPU count for the node is 0.
To Reproduce
Steps to reproduce the behavior:
Create a cluster with no GPU-enabled nodes.
Install Kubecost with kubecostProductConfigs.customPricesEnabled = true in the values.yaml. The default pricing values will work to demonstrate the bug.
Navigate to the Cost Allocation page and see __idle__ GPU costs.
Expected behavior
GPU costs should be $0.
Screenshots
The text was updated successfully, but these errors were encountered:
I will do a bit of digging to see if I can help narrow down the cause, but assigning to @dramich since it's a good chance to dive into a messy bit of the code base :)
Describe the bug
When using a custom pricing model, GPU prices can be assigned to __idle__ costs, even though the GPU count for the node is 0.
To Reproduce
Steps to reproduce the behavior:
kubecostProductConfigs.customPricesEnabled = true
in the values.yaml. The default pricing values will work to demonstrate the bug.Expected behavior
GPU costs should be $0.
Screenshots
The text was updated successfully, but these errors were encountered: