Kubecost VS Spot.io

To find these areas and to generally get a better understanding of your cost structure, e.g. Which team causes which cost, you should monitor the cost. For this, tools such as Kubecost or Replex can be very helpful. - Source: dev.to / almost 2 years ago

However, the overview of the cloud providers can only give you a basic understanding that is only limitedly helpful for multi-tenant Kubernetes clusters and of course is not available in private clouds. Therefore, it often makes sense to use additional tools to measure your Kubernetes usage and costs. Some useful tools in this area are Prometheus, Kubecost, and Replex. - Source: dev.to / almost 2 years ago

Kubecost - analyse cost of the cluster https://kubecost.com/. Source: almost 2 years ago

+1 In my previous stint, I had worked with Spot (https://spot.io/) as one of our vendors. Absolutely great product, amazing customer support and ability to take feature requests, or otherwise address our pain points quickly and effectively. - Source: Hacker News / 11 days ago

FWIW, I am also a big spot.io fan for our workload. During the holidays I run 30-50% spot instances and run 100% spot most of the year. Source: over 1 year ago

Also, you definitely should look into Reservations, and (sale pitch coming) Spot can help you manage those. Source: over 1 year ago

All of this is on spot-instances. We used spot.io (I believe the product is called "Ocean") and they basically took care of all the backend logic to make spot-instances available for the ECS cluster. Source: about 2 years ago

Does cloud provider matter? I would say/think so. Not just cloud provider, but further more, how you set it up, which begets cloud provider. Are you setting it up with only the aws cli? Or did you terraform it? Maybe you chose a particular terraform module or maybe you used eksctl. Maybe you used kops or kubeadm. All these things matter when you get to cluster autoscaling, tainting particular node types to... Source: almost 3 years ago