Skip to main content

2 posts tagged with "aks"

View All Tags

· 3 min read
Matt Ray

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.

AKS Cost Analysis: Namespaces View 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.

AKS Cost Analysis: Cluster View 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.

· 3 min read
Matt Ray

Understanding Kubernetes cloud costs can be a challenge that many teams lack the necessary tools and visibility to solve. In response to this challenge, the CNCF launched the OpenCost project with code provided by Kubecost, which provides an open-source Kubernetes cost monitoring standard for the industry. Microsoft is now giving users of Azure Kubernetes Service (AKS) better cost transparency and contributing to the OpenCost project on behalf of their customers. Without proper cost monitoring tools like OpenCost, teams using Kubernetes may struggle to grasp their expenditures and the factors driving their costs, making it difficult to optimize their infrastructure. By leveraging OpenCost, teams can take their first step towards understanding and improving the efficiency of their Kubernetes cloud spend.

Microsoft Azure

We’re excited to announce that Microsoft has joined the OpenCost community as a contributing partner and is bringing new functionality to both AKS and the OpenCost community. Microsoft’s initial contributions improve their cost reporting and make it easier to export OpenCost data to other reporting platforms.

Documentation Distributed under CC BY 4.0.  The Linux Foundation® (TLF) has registered trademarks and uses trademarks. For a list of TLF trademarks, see: Trademark Usage.