For the latest version of this help, see: https://help.apptio.com/en-us/cloudability/product/k8s-cost-allocation.htm
When utilizing containerized infrastructure, traditional methods of providing visibility into which teams, apps, and services are utilizing which portions of your overall infrastructure can fall short.
Using the Container Cost Allocation tool within Cloudability, you can accurately allocate costs by Kubernetes Clusters, Namespaces, Services, and Labels.
Allocation and Idle Resources
If a pod is in the guaranteed Quality of Service tier, as the amount of resources requested is reserved, we utilize the request data for allocation.
If a pod is classified as burstable, we utilize larger of either the request or usage information for allocation.
If a pod is classified as best effort, we leverage the usage information for allocation.
We provide two methods of looking at idle resources in your clusters. By default, the cost of idle resources is bucketed separately. You can also distribute the idle cost across a given dimension, based on % share of the total cost during that time-frame.
To source resource costs for allocation, we default to Cost (Adjusted). If you do not utilize a Cost (Adjusted) metric, we use Cost (Total) in the calculation.
How it works
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 idle resources in your clusters. Get Started.