Container technology adoption is gaining momentum. By definition a container is a shared service across teams, applications and underlying resources. The challenge is to get visibility to properly allocate container usage to the right cost centers (business units, teams, apps, and/or services) for chargebacks.
This is compounded by the fact that you have both used and unused container resources that you are paying for and need to allocate.
- Collect accurate utilization and allocation data from Kubernetes
- Allocate the right portion of each container to the correct cost center by Kubernetes Clusters, Namespaces, Services and Labels
- Manage allocation of unused resources
A common pattern that Kubernetes implementations follow is to use Namespaces to indicate a team, app, or cost center that is responsible for a portion of a cluster. Often this is done to attach authorization policies to portions of a cluster, but can also be used to allocate costs along the namespace boundary.
Allocation and Unallocated Resources
We provide two methods of looking at unallocated resources in your clusters. By default, the unallocated cost is bucketed separately. You can also distribute the unallocated cost across a given dimension, based on % share of the total cost during that time-frame.
Collecting Kubernetes Data
The Cloudability collection agent compiles metrics from your Kubernetes clusters and sends them to Cloudability for analysis. Using native metric sources, we allocate cost, and provide insight into unallocated resources in your clusters. The agent data sampling frequency is configurable.
The Cloudability Metrics Agent supports Kubernetes Versions 1.6 and newer.
Supported Kubernetes Configurations
See latest supported configurations here.