Closed YannCoderre closed 2 years ago
Our idle cost includes shared namespace cost. For the time being we are not passing on the idle cost value to our namespace owners/users. We will be disabling the shared cost of operation in order to be better assess our baseline cost. And then we can determine the pricing model for our service.
Describe the bug
We need to investigate in the IDLE is actually working properly or is not displaying the actual / right costs. We need to figure what IDLE does and how it works.
This is an example:
In KUBECOST (https://kubecost.aaw.cloud.statcan.ca/)
I find this to be very expexsive for one run.
TO BE COMPARED with:
namespace: aaw-demos
Environment info
Namespace: eric-fecteau
Notebook/server: (none provided)
Expected behaviour
To be investigated
Screenshots
Additional context
As we are now proceeding to start charging the majority of our clients, we need to have a clear understanding of the cost as well to make sure that the costs are actual representing the correct numbers.