5 ms·

Building Open-source cost monitoring for Kubernates

3 points by anuragvishwa 3y ago

We are building open source cost monitoring / visibility for Kubernates on top of Opencost. - It would work for all 3 major clouds (AWS,Azure,GCP). - It would have cost visibility of almost all the types which are required by a team (Namespace, Container, Pods, Network , Cluster level). - It would support multiple clusters. - It would get installed with 1 command. - It would also provide VPA recommendations for cost savings and bin packaging. - It would have alerts generation and connecting to various platform (Slack, email, discord etc.) - It would have feature to generate report and send it to connected platform. - It is a layer built on top of Opencost with near UI/UX for getting cost insights . What would be your suggestions and feedback about this product. It would be open source, would you like to use it.

myid126 3y ago
i'm interested, could you show your project,please.
- anuragvishwa 3y ago
  It is build in progress, wanted to know the feedback/need of the product before launching. Nevertheless, it would get launched by Jan 30th 2024 . The sample page would look like this - https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.it%2Fly0udmd4gs8c1.png%3Fwidth%3D2358%26format%3Dpng%26auto%3Dwebp%26s%3D81f625e4644c365e1eb234f2bb1e6ad43e8ec06e&rdt=43735 https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.... I would keep posting the updates to the project here. Thanks for going through the context.
  - gus_massa 3y ago
    It's very difficult to get traction here until the project is launched (or at least you have a bunch of screenshots to show).
deleted 3y ago
[deleted]
uaas 3y ago
My feedback/suggestions based on this summary: call it Kubernetes, and make it clearer how it is different from existing tools.
- anuragvishwa 3y ago
  With comparison to say Kubecost , the product will have - - Muticluster visibility in the single dashboard (for Kubecost , muticluster is enterprise ). - The application would also contain apart from monitoring Autoscaling and bin packing ( based on VPA recommendation for each application and providing a window to automatically adjust it). - Smart cost optimization : Tools like Karpenter(AWS) would be used to quickly get the alternatives to On-Demand instances and providing spot instances for them. - Better UX - The UX would be our top priority with 5 min, setup , maybe with a helm package. - Automated rightsizing : Based on the VPA recommendation . These are the basic points i could ponder on for the application. 1. The monitoring part would be open-source and free for multi clusters. 2. Report generation and alert management to (Slack,email etc) open-source. 2. The autoscaling part/Bin packaging/Node autoscaling/Spot instances would be enterprise features. Would love to know your insights and feedback . Thanks for going through the context.
  - uaas 3y ago
    I would start with Helm from day 1, given its (and GitOps movement’s) popularity. I don’t really see any benefit to have a “single command” install in the ops world. The e.g. Helm equivalent is also a one-liner, and most other artisan CLIs and similar solutions are not production ready implementations, which is something I would want from any tool in this space.
    - anuragvishwa 3y ago
      Sorry for the confusion, but by single command , i meant to say single Helm command!
gtirloni 3y ago
That's basically OpenCost Enterprise. https://www.opencost.io/enterprise https://www.opencost.io/enterprise
- anuragvishwa 3y ago
  With comparison to say Kubecost , the product will have - - Muticluster visibility in the single dashboard (for Kubecost , muticluster is enterprise ). - The application would also contain apart from monitoring Autoscaling and bin packing ( based on VPA recommendation for each application and providing a window to automatically adjust it). - Smart cost optimization : Tools like Karpenter(AWS) would be used to quickly get the alternatives to On-Demand instances and providing spot instances for them. - Better UX - The UX would be our top priority with 5 min, setup , maybe with a helm package. - Automated rightsizing : Based on the VPA recommendation . These are the basic points i could ponder on for the application. 1. The monitoring part would be open-source and free for multi clusters. 2. Report generation and alert management to (Slack,email etc) open-source. 2. The autoscaling part/Bin packaging/Node autoscaling/Spot instances would be enterprise features. Would love to know your insights and feedback . Thanks for going through the context

3 points by anuragvishwa 3y ago

myid126 3y ago

i'm interested, could you show your project,please.

anuragvishwa 3y ago
It is build in progress, wanted to know the feedback/need of the product before launching. Nevertheless, it would get launched by Jan 30th 2024 . The sample page would look like this - https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.it%2Fly0udmd4gs8c1.png%3Fwidth%3D2358%26format%3Dpng%26auto%3Dwebp%26s%3D81f625e4644c365e1eb234f2bb1e6ad43e8ec06e&rdt=43735 https://www.reddit.com/media?url=https%3A%2F%2Fpreview.redd.... I would keep posting the updates to the project here. Thanks for going through the context.
- gus_massa 3y ago
  It's very difficult to get traction here until the project is launched (or at least you have a bunch of screenshots to show).

deleted 3y ago

[deleted]

uaas 3y ago

My feedback/suggestions based on this summary: call it Kubernetes, and make it clearer how it is different from existing tools.

anuragvishwa 3y ago
With comparison to say Kubecost , the product will have - - Muticluster visibility in the single dashboard (for Kubecost , muticluster is enterprise ). - The application would also contain apart from monitoring Autoscaling and bin packing ( based on VPA recommendation for each application and providing a window to automatically adjust it). - Smart cost optimization : Tools like Karpenter(AWS) would be used to quickly get the alternatives to On-Demand instances and providing spot instances for them. - Better UX - The UX would be our top priority with 5 min, setup , maybe with a helm package. - Automated rightsizing : Based on the VPA recommendation . These are the basic points i could ponder on for the application. 1. The monitoring part would be open-source and free for multi clusters. 2. Report generation and alert management to (Slack,email etc) open-source. 2. The autoscaling part/Bin packaging/Node autoscaling/Spot instances would be enterprise features. Would love to know your insights and feedback . Thanks for going through the context.
- uaas 3y ago
  I would start with Helm from day 1, given its (and GitOps movement’s) popularity. I don’t really see any benefit to have a “single command” install in the ops world. The e.g. Helm equivalent is also a one-liner, and most other artisan CLIs and similar solutions are not production ready implementations, which is something I would want from any tool in this space.
  - anuragvishwa 3y ago
    Sorry for the confusion, but by single command , i meant to say single Helm command!

gtirloni 3y ago

That's basically OpenCost Enterprise. https://www.opencost.io/enterprise https://www.opencost.io/enterprise

anuragvishwa 3y ago
With comparison to say Kubecost , the product will have - - Muticluster visibility in the single dashboard (for Kubecost , muticluster is enterprise ). - The application would also contain apart from monitoring Autoscaling and bin packing ( based on VPA recommendation for each application and providing a window to automatically adjust it). - Smart cost optimization : Tools like Karpenter(AWS) would be used to quickly get the alternatives to On-Demand instances and providing spot instances for them. - Better UX - The UX would be our top priority with 5 min, setup , maybe with a helm package. - Automated rightsizing : Based on the VPA recommendation . These are the basic points i could ponder on for the application. 1. The monitoring part would be open-source and free for multi clusters. 2. Report generation and alert management to (Slack,email etc) open-source. 2. The autoscaling part/Bin packaging/Node autoscaling/Spot instances would be enterprise features. Would love to know your insights and feedback . Thanks for going through the context