kuberhealthy
A Kubernetes operator for running synthetic checks as pods. Works great with Prometheus!
Runs with mockssource: 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, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Go binary compiles and all tests pass across cmd/kuberhealthy (16 subtests), internal/kuberhealthy (20+ subtests), internal/metrics (1), pkg/checkclient (2 subtests), and pkg/nodecheck (1). Binary requires a Kubernetes cluster for full launch; test suite uses fakes/mocks and completes successfully.
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.
- Go (golang) compiler not found in container3 minutes
- Install time
- 3 minutes
- Cold machine to finish
- 13 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- go test -v ./cmd/kuberhealthy ./internal/kuberhealthy ./internal/metrics ./pkg/checkclient ./pkg/nodecheck exited 0, all tests PASS
- Model tokens used
- 73,926
- 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
- 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.
- Documentation files exist in `docs/agent/` with ALL-CAPS names, and `docs/README.md` / `docs/HTTP… tokens used 73,926 All good. Now let me produce the final report. Here is the complete report from my work on this repository. **What I did:** - This is the **Kuberhealthy** project (V3), a Kubernetes-native synthetic monitoring operator writ… - Go (v1.26.5) was not installed in the container — I downloaded and extracted the official binary … - The project builds successfully: `go build ./cmd/kuberhealthy` produced a 44MB ELF binary. - Full test suite passes across all packages. - The binary runs (exits with Kubernetes config error, expected in a non-K8s environment), and the … - Documentation files exist in `docs/agent/` with ALL-CAPS names, and `docs/README.md` / `docs/HTTP…
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 3 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
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.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.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.
[](https://argusic.com/subject/kuberhealthy)Questions
- Does kuberhealthy run?
- kuberhealthy runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 1 error 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. One attempt is 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.05: 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?
- 3 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?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for kuberhealthy?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.