search

kubecost / features-bugs

A public repository for filing of Kubecost feature requests and bugs. Please read the issue guidelines before filing an issue here.
0 stars 0 forks source link

Unmounted PVCs appearing under Abandoned workloads #38

Closed keithhand closed 1 month ago

keithhand commented 1 year ago

Describe the bug
On the abandoned workloads savings page, PVCs deployed to the cluster have a line item for "x-unmounted-pvcs," regardless if those PVCs are attached to a pod. Perhaps this is intended. Still, it seems to pull all "-unmounted-pvc" values.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the Abandoned workload savings page and look for "-unmounted-pvc" values

Expected behavior
I'm unsure how we expect to show "abandoned pvcs" since this page is related to traffic, and I'm unsure how that metric relates to PVCs. An explanation on the page to describe how to interpret this data would be helpful.

Screenshots
image

What impact will this have on your ability to get value out of Kubecost? This helps clarify what the information on this page is trying to portray.

Please share the support case, if any
ZD 4488

kwombach12 commented 1 year ago

@keithhand Please correct me if I'm wrong, but this sounds like you'd like some more context/useful information for the case where a user expands an unmounted pvc in the abandoned workloads savings page. I am fully supportive of this, but it sounds more like a Feature Request than a bug to me. Am I missing something?

keithhand commented 1 year ago

I'm not 100%, tbh. This page is based on data transferred to/from pods, so the fact that PVCs are included on this page feels like a bug to me. Mainly because there's never going to be data transferred to/from PVCs, I'm not sure if they should be showing up on this page at all.

kwombach12 commented 1 year ago

@keithhand Gotcha. Given this is WAI, I will mark as a FR for now and I will start exploring whether it makes sense to remove the PVCs from this page.

chipzoller commented 1 month ago

Hello, in an effort to consolidate our bug and feature request tracking, we are deprecating using GitHub to track tickets. If this issue is still outstanding and you have not done so already, please raise a request at https://support.kubecost.com/.