4 ms·
My feedback/suggestions based on this summary: call it Kubernetes, and make it clearer how it is different from existing tools.
by 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 agoWith 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 agoI 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 agoSorry for the confusion, but by single command , i meant to say single Helm command!