Centralized Cost Monitoring
Monitoring costs of all attached clusters with Kubecost
Kubecost, running on Kommander, provides centralized cost monitoring for all attached clusters. This feature, installed by default in the management cluster, provides a centralized view of Kubernetes resources used on all attached clusters.
By default, up to 15 days of cost metrics are retained, with no backup to an external store.
Centralized Costs
Using Thanos, the management cluster collects cost metrics remotely from each attached cluster. Costs from the last day and the last 7 days are displayed for each cluster, workspace, and project in the respective DKP UI pages. Further cost analysis and details can be found in the centralized Kubecost UI running on Kommander, at:
https://<CLUSTER_URL>/dkp/kommander/kubecost/frontend/detail.html#&agg=clusterFor more information on cost allocation metrics and how to navigate this view in the Kubecost UI, see the Kubecost docs on Kubernetes Cost Allocation.
To identify the clusters in Kubecost, use the cluster’s monitoring ID. The monitoring ID corresponds to the kube-system namespace UID of the cluster. To find the cluster’s monitoring ID, select the Clusters tab on the DKP UI in the relevant workspace, or go to the Clusters page in the Global workspace:
https://<CLUSTER_URL>/dkp/kommander/dashboard/clustersSelect View Details on the attached cluster card. Select the Configuration tab, and find the monitoring ID under Monitoring ID (clusterId).
You can also search or filter by monitoring ID on the Clusters page.
To look up a cluster’s kube-system namespace UID directly using the CLI, run the following kubectl command, using the cluster’s context or kubeconfig.
kubectl get namespace kube-system -o jsonpath='{.metadata.uid}'Kubecost
Kubecost integrates directly with the Kubernetes API and cloud billing APIs to give you real-time visibility into your Kubernetes spend and cost allocation. By monitoring your Kubernetes spend across clusters, you can avoid overspend caused by uncaught bugs or oversights. With a cost monitoring solution in place you can realize the full potential and cost of these resources and avoid over-provisioning resources.
To customize pricing and out of cluster costs for AWS, you must apply these settings using the Kubecost UI running on each attached cluster. You can access the attached cluster’s Kubecost Settings page at:
https://<MANAGED_CLUSTER_URL>/dkp/kubecost/frontend/settings.html
Make sure you access the cluster's Kubecost UI linked above, not the centralized Kubecost UI running on the Kommander management cluster.
AWS
For more accurate AWS Spot pricing, follow these steps to configure a data feed for the AWS Spot instances.
To allocate out of cluster costs for AWS, visit this guide.
Grafana dashboards
A set of Grafana dashboards providing visualization of cost metrics is provided in the centralized Grafana UI:
https://<CLUSTER_URL>/dkp/kommander/monitoring/grafanaThese dashboards give a global view of accumulated costs from all attached clusters. From the navigation in Grafana, you can find these dashboards by selecting those tagged with cost, metrics, and utilization.
Related Information
For information on related topics or procedures, refer to the following: