kuberhealthy

A Kubernetes operator for running synthetic checks as pods. Works great with Prometheus!

Runssource: GitHubhomepageGoApache-2.0commit ab3f163197f8

Go, Apache-2.0 licensed. The project labels itself: cicd, continuous delivery, continuous integration, continuous testing, health, kubernetes, monitoring and operator.

kuberhealthy runs. An Argusic agent installed it in 25 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The Kuberhealthy v3 controller builds, its full Go test suite passes, it runs as leader against a real kube-apiserver/etcd control plane, serves all documented HTTP endpoints with 200, and completes a HealthCheck run from schedule to checker-pod creation to report to updated /json status and Prometheus 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 96 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
96 / 100
cost of the verifying run
$0.11 (measured)
recorded runs
2
last tested
stars
2,282
forks
293
open issues
5
watchers
26
size
35 MB
created
last push

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.

Time lost to each failure while testing kuberhealthy, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • no Go toolchain in container; go command not found12 minutes
  • first HealthCheck I created had container-level restartPolicy which the API server correctly rejected (Forbidden: may not be set for non-init containers); controller recorded pod-creation failures6 minutes
  • kubeconfig CA pointed at a self-signed CA that did not sign the apiserver serving cert; controller startup failed with x509 unknown authority against kube-apiserver4 minutes
  • GET /openapi.yaml returned 500 when the binary was launched with a working directory lacking ./openapi.yaml (handler reads relative path; my harness cwd was /home/runner)3 minutes
Install time
25 minutes
Cold machine to finish
11 minutes
Errors hit and fixed
4 hit, 4 fixed with no human help
How the result was proved
go test ./... with -count=1 passed all packages with 48 passing tests; controller binary launched and acquired the leader lease; curl to http://127.0.0.1:8080 returned 200 on /, /json, /metrics, /healthz, and /openapi.yaml; POST /check with the run UUID echoed from the created pod returned 200 and /json then showed demo-check ok:true with successCount:1 while /metrics showed kuberhealthy_check{check=...demo-check...,status="1"} 1
Model tokens used
452,178
Exact commit tested
ab3f163197f8
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

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 1, run . The verdict above comes from a different attempt, so read this as one session and not as the current result. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

/bin/sh -lc 'cd /work/repo && git status --short; echo "CLEAN_CHECK_DONE"; date -u +%H:%M:%S' in /w…
 succeeded in 0ms:
CLEAN_CHECK_DONE
19:27:00
exec
/bin/sh -lc "echo \"final quick sanity:\"; /home/runner/kuberhealthy --version 2>&1 | head -1; curl…
 succeeded in 0ms:
final quick sanity:
time="2026-11-11T19:27:08Z" level=warning msg="Failed to open namespace file: open /var/run/secrets…
controller still up, /json=200
tokens used
452,178

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

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 25 minutes.
  • Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
  • Ran without a GPU, so it does not need one to start.
  • Licensed Apache-2.0, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.

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 byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.11
Argusic Runner1/3Runs with mocks92.000.05

Topics (from GitHub)

cicdcontinuous-deliverycontinuous-integrationcontinuous-testinghealthkubernetesmonitoringoperatorsynthetic

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/kuberhealthy.svg)](https://argusic.com/subject/kuberhealthy)

Questions

Does kuberhealthy run?
Yes. kuberhealthy runs. Argusic installed and launched it on a clean machine in 25 minutes, hitting 4 errors on the way, and recorded the session.
How did Argusic test kuberhealthy?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ab3f163197f8. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test kuberhealthy?
The run that produced this verdict cost $0.11: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does kuberhealthy take to install?
25 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 kuberhealthy need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing kuberhealthy?
4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for kuberhealthy?
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.

Discussion