Wrapping up this series, following our previous Cloud FinOps - Part 4: Kubernetes Cost Report, this final piece looks at how to increase visibility of underutilized workloads.
This blog post is a continuation of Cloud FinOps - Part 3: Cloud Cost Report [https://medium.com/empathyco/cloud-finops-part-3-cloud-cost-report-865a81c03c1c] , in which we will explore how to gain cost visibility on Kubernetes Workloads. Motivation Nowadays, a lot of companies run their workloads on Kubernetes because there are many benefits to
Following our previous posts on Cloud FinOps Principles [https://medium.com/empathyco/cloud-finops-part-1-principles-79b88aeeab4f] and Tag Allocation [https://medium.com/empathyco/tag-allocation-strategy-part-2-3c7f8595186a] Strategy, it is time to unveil the third piece in the series. In this post, we will focus how to develop a solution for visualizing cloud costs. Introduction The
In the first post [https://engineering.empathy.co/cloud-finops-part-1-principles/] of this four-part series, we explored the Cloud FinOps principles and the key milestones in the journey to start walking in FinOps: * Tag Allocation Strategy * Cost Report * Usage Report In this post, we’ll dig deeper into a crucial step in
FinOps, short for Cloud Financial Operations, helps teams optimise cloud costs to get the most value for their projects. Teams adopt best practices and a collaborative culture to manage cloud operations with greater financial accountability: balancing cost, speed and quality. When your teams have problems managing their cloud costs, following