Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allocation API has GPU costs when GPU count is 0 #1389

Closed
keithhand opened this issue Apr 26, 2022 · 3 comments · Fixed by opencost/opencost#1193
Closed

Allocation API has GPU costs when GPU count is 0 #1389

keithhand opened this issue Apr 26, 2022 · 3 comments · Fixed by opencost/opencost#1193
Assignees
Labels
bug Something isn't working v1.94

Comments

@keithhand
Copy link
Contributor

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:

  1. Create a cluster with no GPU-enabled nodes.
  2. Install Kubecost with kubecostProductConfigs.customPricesEnabled = true in the values.yaml. The default pricing values will work to demonstrate the bug.
  3. Navigate to the Cost Allocation page and see __idle__ GPU costs.

Expected behavior
GPU costs should be $0.

Screenshots
image

@keithhand keithhand added the bug Something isn't working label Apr 26, 2022
@AjayTripathy
Copy link
Contributor

I wanted to note that a quick workaround here is to set GPU prices to 0 in your default pricing settings.

@AjayTripathy
Copy link
Contributor

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 :)

@Adam-Stack-PM
Copy link

@dramich any update here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v1.94
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants