kuberhealthy tested by Argusic Runner

Attempt 2 of 3 · Runs · Argusic Score 100.0 of 100

all runs of kuberhealthycicdcontinuous-deliverycontinuous-integrationcontinuous-testinghealthkubernetes

Session recording

Loading recording...

Download the original recording · fingerprint d6a1d2ec90343bb2...

What the test found

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.

Booted real kube-apiserver v1.28.0 plus etcd v3.5.15 from official binaries, registered the HealthCheck CRD and namespace, and ran the built controller binary as leader; exercised the full schedule->checker-pod->report lifecycle and the documented HTTP API. Controller (pid 14897), kube-apiserver, and etcd were still up at final verification.

Argusic installed kuberhealthy in 25 minutes and launched it; verification reached Verified running for real. 4 of 4 recorded errors were worked through (see the timeline below).

Runsall runs of kuberhealthy

This summary is drawn from the agent's recorded report for this run. Every figure traces to the log and recording above; nothing here is authored.

Error and fix timeline

No errors were recorded for this run.

Discussion