Kubecost

Hi, I started using Kubecost few weeks ago, but I was shocked at how easy it was to install to our cluster, also has a feacher rich list to provisioning our cluster requests/limits. Only one improvment I would like to mention it's the official documentation. It is a little underrated imho, but guys I love your product, keep up the good work!

I absolutely loved using Kubecost to monitor and manage my Cluster costs and save on the monthly bills. The UI is so clean and precise that you won't miss a single detail. You get all the insights to your cluster usages and also Kubecost suggests ways to optimize the usages and save more with each bill cycle. You can also have billing alerts and governance on the go. With Kubecost in the house, you wallet is gonna really feel healthy and full.

Pros: Adopts standardized tooling for deployment/management ( helm/prometheus/etc. ) Clean and easy to use UI Can start providing value within a very short timeframe of being setup Strong API support for integrating into more bespoke use cases ( as well as existing integrations with the likes of kubelens ) Strong open core base, with great support through slack Cons: Self hosted. Not inherently a con depending on use case but does provide a small degree of management overhead Documentation could use some work Alerting is a little bit limited --- I've been using kubecost for a while now and it's become increasingly relevant as we've been transitioning from startup to scale-up and our priorities around opex have changed. There's two areas where kubecost really excels for our use case: 1. The ability to get insight into where we can make cost optimizations for our kubernetes cluster. Being able to identify where we had a lot of wasted resources, unoptimized instance sizing and limited use of limits/etc. within kubernetes is a big win. Especially with dynamic workloads which can be scaled on demand. 2. An area we're just beginning to explore, which is utilizing kubecost in order to associate costs with internal teams and with customer usage. This is the kind of problem I've had to solve a few times elsewhere, but generally have ended up rolling my own sub-optimal solution. While we haven't ended up fully leveraging this capability yet, the early proof of concepts we've done really show how kubecost can shine for this kind of challenge. Ultimately, for me kubecost excels at bridging the gap between base cloud cost reporting (for infrastructure used ) and extending that through to workload cost management. As kubernetes increasingly becomes a kind of universal compute engine, that gap of data becomes increasingly painful to deal with. So yeah. Very impressed and super excited to see where the product goes in the future.