kube-state-metrics
Add-on agent to generate and expose cluster-level metrics.
Runs with mockssource: GitHubhomepageGoApache-2.0commit f77f1b8c3bb7
Go, Apache-2.0 licensed. The project labels itself: kubernetes, kubernetes exporter, kubernetes monitoring, metrics, monitoring, observability, prometheus and prometheus exporter.
kube-state-metrics runs, with stand-ins for the services it depends on. An Argusic agent installed it in 8 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Binary builds (87MB), all 17 unit test packages pass with -race, server starts and serves HTTP 200 on /healthz, /livez, /readyz, self-metrics (Go runtime) on port 8081, but requires a real Kubernetes API server to produce kube_ metrics.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- kube-state-metrics requires a Kubernetes API server to serve kube_ metrics. Minimal mock stub doesn't handle client-go protobuf watch protocol, so main /metrics returns 0 bytes (200 OK).2 minutes
- Go not installed in container. 'go' command not found.1 minute
- Install time
- 8 minutes
- Cold machine to finish
- 12 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- go test -count=1 -race ./internal/... ./pkg/... ./tests/lib/... exited 0, all 17 packages passed. Binary launched with --kubeconfig pointing at mock API server: curl http://localhost:8080/healthz returned 200; curl http://localhost:8080/livez returned 200; curl http://localhost:8081/readyz returned 200; curl http://localhost:8081/metrics returned Go runtime and process metrics; curl http://localhost:8080/metrics returned HTTP 200 with 0 bytes because no kube resources populated (expected with mock).
- Model tokens used
- 225,563
- Exact commit tested
- f77f1b8c3bb7
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
ok k8s.io/kube-state-metrics/v2/pkg/metricshandler 1.046s ok k8s.io/kube-state-metrics/v2/pkg/optin 1.014s ok k8s.io/kube-state-metrics/v2/pkg/options 1.013s ok k8s.io/kube-state-metrics/v2/pkg/sharding 1.017s ok k8s.io/kube-state-metrics/v2/pkg/util 1.031s ok k8s.io/kube-state-metrics/v2/pkg/util/proc 1.008s ok k8s.io/kube-state-metrics/v2/pkg/watch 1.025s ok k8s.io/kube-state-metrics/v2/tests/lib 2.024s All 17 unit test packages pass. Now for the final summary. tokens used 225,563 All 17 unit test packages pass. Now for the final summary.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 8 minutes.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.08 | |
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.04 |
Topics (from GitHub)
kuberneteskubernetes-exporterkubernetes-monitoringmetricsmonitoringobservabilityprometheusprometheus-exporter
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kube-state-metrics)Questions
- Does kube-state-metrics run?
- kube-state-metrics runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 8 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test kube-state-metrics?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f77f1b8c3bb7. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test kube-state-metrics?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does kube-state-metrics take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does kube-state-metrics need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing kube-state-metrics?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for kube-state-metrics?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.