11 posts tagged with "integrations"

Reposted from the Headlamp blog post: Streamlining Kubernetes Cost Management with the New OpenCost Plugin for Headlamp, by Santhosh Nagaraj

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.

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.

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.

Who are Port and OpenCost?​

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:

• Oracle Cloud Infrastructure support has been added, enabling Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) users to track their Cost Allocations across their deployments.
• Additional patches for Docker have been merged, making it easier to track Cloud Costs without requiring Kubernetes to be installed. This will allow Cloud Costs and other non-Kubernetes functionality to be accessed wherever you may need it.
• The OpenCost and OpenCost-UI containers have been moved to the GitHub Container Registry. The OpenCost Helm Chart, the Prometheus OpenCost Exporter, and the OpenCost manifest are all being updated to reflect the new download location.
• The OpenCost UI now shows the version of OpenCost being used in the footer. This is included in the startup logging of each container as well, but it should help make debugging a little easier.

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

We are pleased to announce that OpenCost is being integrated into Microsoft’s new Azure Kubernetes Service (AKS) Cost Analysis tool to enable usage metrics collection. Microsoft Azure customers can now experience native visibility of cost allocation based on Kubernetes-specific constructs.

AKS Cost Analysis is an add-on for Standard and Premium-tier AKS clusters offered to customers at no additional cost. It provides cost allocation reports directly in the Azure portal. AKS customers can now easily visualize their Kubernetes cost allocations as the foundation for further optimization and anomaly detection.

New Kubernetes Namespaces view.

AKS is also the first Azure service that drills down into the specifics of the service’s granular cost details. These Kubernetes-specific views will surface cost allocation across AKS cluster resources (i.e. VMs, public IPs, disks, etc.). "Our goal in Microsoft Azure is to build Kubernetes-centric experiences on top of vendor-neutral open-source solutions, ensuring that our customers can take advantage of the innovation and portability of the CNCF ecosystem natively in Azure,” said Sean McKenna, Director of Product Management for Azure Cloud Native. “We've really enjoyed partnering with the OpenCost community on this project and are thrilled to get it in the hands of our customers." AKS customers will be able to configure how shared costs are allocated across namespaces.

New Kubernetes Cluster view.

OpenCost is the open source CNCF sandbox project and specification for the real-time monitoring of cloud costs and associated Kubernetes deployments. It models and tracks current and historical Kubernetes cloud spend and resource allocation as well as general cloud costs, which may be used as the basis for cost observability and optimizations. Check out the code on GitHub or join the community.

Microsoft announced their involvement with OpenCost earlier this year and have been active in the community ever since. Today’s announcement is just another great step in our journey together. Microsoft has committed to helping establish OpenCost as the open source standard for Kubernetes and cloud costs monitoring. If you want to run your own OpenCost deployment, we have Azure-specific instructions, including accessing your own Price Sheet API and configuring Azure Cloud Cost access.

As more AKS users get visibility and understanding of their Kubernetes cloud billing, we’re sure they’ll join us in our goal of building more consistency across all providers. As we continue to ship new features, AKS users will continue to benefit from OpenCost’s success.

We're excited to announce that the OpenCost plugin for Backstage is now available in the latest release (v1.18.0). With the OpenCost plugin, Backstage users can now view and access their Kubernetes cloud costs directly in their developer portals.

Reposted from the VictoriaMetrics blog: Monitoring Kubernetes costs with OpenCost and VictoriaMetrics

Original author: Zakhar Bessarab