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
In Google Cloud each vCPU and each GB of RAM have a fixed price. Kube Eagle can easily aggregate the allocatable and in use CPU & RAM and add a pricing metric for that.
This way one could get an overview how expensive a namespace or deployment is and what saving potential it has (usage compared to allocatable resources).
Challenges:
How to define the CPU / RAM pricing? Each zone, provider and machine type (e. g. spot instances, on demand, preemptible, commitment) may have a slightly different CPU & RAM pricing
The text was updated successfully, but these errors were encountered:
Hi @weeco, we've recently done this across multiple cloud providers in the Kubecost project (https://github.com/kubecost/cost-model). It could be really cool to collaborate on this if you're interested! Let me know if you want to talk some about it -- [email protected]
In Google Cloud each vCPU and each GB of RAM have a fixed price. Kube Eagle can easily aggregate the allocatable and in use CPU & RAM and add a pricing metric for that.
This way one could get an overview how expensive a namespace or deployment is and what saving potential it has (usage compared to allocatable resources).
Challenges:
The text was updated successfully, but these errors were encountered: