How To Setup Kube State Metrics on Kubernetes

Setup Kube State Metrics on Kubernetes

In this blog, we will look at what is Kube State Metrics and its setup on Kubernetes. This blog is part of the Prometheus kubernetes setup tutorial series.

What is Kube State Metrics?

Kube State metrics is a service that talks to the Kubernetes API server to get all the details about all the API objects like deployments, pods, daemonsets, Statefulsets, etc.

Primarily it produces metrics in Prometheus format with the stability as the Kubernetes API. Overall it provides kubernetes objects & resources metrics that you cannot get directly from native Kubernetes monitoring components.

Kube state metrics service exposes all the metrics on /metrics URI. Prometheus can scrape all the metrics exposed by Kube state metrics.

Following are some of the important metrics you can get from Kube state metrics.

  1. Node status, node capacity (CPU and memory)
  2. Replica-set compliance (desired/available/unavailable/updated status of replicas per deployment)
  3. Pod status (waiting, running, ready, etc)
  4. Ingress metrics
  5. PV, PVC metrics
  6. Daemonset & Statefulset metrics.
  7. Resource requests and limits.
  8. Job & Cronjob metrics

You can check out the detailed supported metrics from the documentation here.

Kube State Metrics Setup

Kube state metrics is available as a public docker image. You will have to deploy the following Kubernetes objects for Kube state metrics to work.

  1. A Service Account
  2. Cluster Role – For kube state metrics to access all the Kubernetes API objects.
  3. Cluster Role Binding – Binds the service account with the cluster role.
  4. Kube State Metrics Deployment
  5. Service – To expose the metrics

All the above Kube state metrics objects will be deployed in the kube-system namespace

Let’s deploy the components. All the deployment objects are available in Github. You can also find the same deployment object in the official repo as well.

Step 1: Clone the Github repo

git clone

Step 2: Create all the objects by pointing to the cloned directory.

kubectl apply -f kube-state-metrics-configs/

Step 3: Check the deployment status using the following command.

kubectl get deployments kube-state-metrics -n kube-system

kube State Metrics Prometheus Config

All the Kube static metrics can be obtained from the Kube state service endpoint on /metrics URI.

This configuration can be added as part of the Prometheus job configuration. You need to add the following job configuration to your Prometheus config for Prometheus to scrape all the Kube state metrics.

Note: If you have followed my prometheus guide, you dont have to add this scrape config. It is already part of the prometheus config. You should see the target status “up” after deploying kube state metrics.

If you have follo

- job_name: 'kube-state-metrics'
    - targets: ['kube-state-metrics.kube-system.svc.cluster.local:8080']
  1. Hi Bibin, thank you for writing this awesome blog.
    I had worked on this setting up kube state metric but faced endpoint is down in Prometheus target and showing error Context Deadline Exceeded.

    1. Hi Shivam, Did you check the Kube state metrics deployment? is it running without any errors?

  2. Hey Bibin, After long search atleast got some good documentation abt kube-state-metrics. thank you for writing it. Do you know how to add this kube-state metrics entry with helm for installing it as automation ??

  3. I have added entry like below (last line). but its not wring. Do i missing anything ? or is this not correct way ?

    helm upgrade –install –tiller-namespace tiller-full –force prometheus stable/prometheus –wait –namespace prometheus –kube-context=${lower(var.environment)}.${data.terraform_remote_state.base_kops_config.base_domain}
    –set rbac.create=true
    –set server.ingress.enabled=true
    –set server.ingress.hosts=”{prometheus.${lower(var.environment)}.${data.terraform_remote_state.base_kops_config.base_domain},prometheus.ingress.${lower(var.environment)}.${data.terraform_remote_state.base_kops_config.base_domain}}”
    –set server.image.tag=”v2.11.1″
    –set kubeStateMetrics.image.tag=”v1.7.0″

Leave a Reply

Your email address will not be published. Required fields are marked *

You May Also Like