The OpenCost project proudly announces that we’ve reached CNCF Incubating status! This milestone in our journey underscores the significant dedication the project has received from the community that contributes to OpenCost. We’d like to thank the developers, Kubernetes practitioners, and FinOps teams from organizations across the globe that continue to make this project meaningful.
Reposted from the Headlamp blog post: Streamlining Kubernetes Cost Management with the New OpenCost Plugin for Headlamp, by Santhosh Nagaraj
Headlamp is an open source Kubernetes UI that focuses on usability and can be extended via plugins. It is available as a web or desktop application. Learn more about it at headlamp.dev.
OpenCost is one of CNCF's leading open-source projects that offers real-time native cost monitoring for Kubernetes environments, providing visibility to developers and companies on the costs linked to their cloud-native applications. With OpenCost, one can trace the costs of single workloads, namespaces, and even particular labels in your Kubernetes cluster. The continuous granular cost visibility that OpenCost provides help in effectual usage of resources and better budgeting.
We are excited to announce that the CNCF OpenCost project has significantly expanded its scope and capabilities beyond existing Kubernetes and cloud costs monitoring. Via the new OpenCost Plugins framework, teams are now increasingly able to use OpenCost to monitor ALL of their IT spending (infrastructure monitoring, data platforms, cloud services or other tools) in one place. We have kicked things off with a Datadog plugin, but this is just the first of many plugins coming to OpenCost.
The new 1.110 release of OpenCost is a huge milestone in the project’s mission to deliver granular, real-time IT costs to the world. Already the leading project for monitoring the costs for Kubernetes and Cloud Services, OpenCost’s new Plugin architecture will provide comprehensive, unified cost monitoring capabilities to developers, FinOps practitioners, platform engineers, or anyone in your organization who values monitoring the cost of your IT resources.
Reposted from the Oracle Developers series by Ali Mukadam: Announcing OpenCost support for OCI
It’s a fact now that Kubernetes has won the container wars. It has fought off Docker, Mesos, OpenStack and a number of other clustering and orchestration technologies to become the de-facto Cloud Operating System. Heck, Kubernetes has even made it to F-16s. You say Maverick is an ace? He’s got nothing on those F-16s pilots who are able to fly a cloud within clouds at Mach 2. I’m jealous of those pilots.
The CNCF OpenCost project is increasing its scope to help environmental sustainability within the tech industry by introducing carbon cost emissions tracking across Kubernetes and cloud spend. This initiative comes as a response to the recognition of the growing environmental impact associated with cloud computing. By integrating carbon cost tracking into its framework, OpenCost aims to empower organizations to make informed decisions about their technology usage, taking into account not only the financial expenses but also the environmental impact.
Kubecost joined efforts with ThoughtWorks and their open source Cloud Carbon Footprint tool to bring resource-level carbon footprint monitoring data into OpenCost.
KubeCon Europe 2024 is coming up next week in Paris March 19-22 and we're looking forward to all the OpenCost news and events!
Reposted from the Port blog: Port & OpenCost: Bringing open source cost monitoring for cloud native environments to developers
Port officially integrates with OpenCost. This brings together OpenCost data and Port’s internal developer portal, providing developers with the autonomy to understand and manage the cost associated with their work as well as providing managers with alerts, scorecards and initiatives that make it much easier to control costs.
OpenCost 1.109.0 is now available and has a host of new features, enhancements, and bug fixes. This release has over 200 commits from 24 individuals and 8 of them are from first-time contributors. This is also the first release with a non-Kubecost Maintainer. Highlights from the release include:
There were many more community-provided enhancements, fixes, and additional tests that were added to continue improving OpenCost. Please join us in the OpenCost community and help build our next great release!
Using OpenCost as a Prometheus metric exporter has long been a supported use case, but now you can get this from the standard Prometheus Community Helm Charts repository. OpenCost is the open source CNCF project for monitoring cloud and Kubernetes infrastructure costs. For users who want to export various cost metrics from OpenCost without setting up any other OpenCost dependencies, the Prometheus OpenCost Exporter makes it easy to get up and running with minimal steps. If you’re using Helm already, it’s as simple as
OpenCost is an open source implementation for Kubernetes cost monitoring and now cloud cost monitoring for AWS, Azure, and GCP. The project makes all of this data accessible via an API and user interface. While discussing the idea of running OpenCost on platforms besides Kubernetes we realized that with this new Cloud Costs feature there are users who want API access to their cloud billing data without needing to run on Kubernetes. I opened the Issue OpenCost without Kubernetes #2268 and as luck would have it, we had our internal Hackathon last week.
If you're not familiar with OpenCost, it's the open source CNCF project for monitoring Kubernetes and cloud spending. It's a Golang implementation of the OpenCost Specification for monitoring Kubernetes cloud costs. It has an optional web UI and you can also run it as a Prometheus metrics exporter. The code is all at https://github.com/opencost/opencost and you can learn more about the project at https://opencost.io
