velero
Backup and migrate Kubernetes applications and their persistent volumes
Runs with mockssource: GitHubhomepageGoApache-2.0commit 8e9f66addf63
Go, Apache-2.0 licensed. The project labels itself: backup, disaster recovery, hacktoberfest, kubernetes and velero.
velero runs, with stand-ins for the services it depends on. An Argusic agent installed it in 30.4 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
Velero binary builds successfully (150MB ELF binary), all 78 unit-test packages pass, and the CLI help text displays correctly. The binary requires a Kubernetes cluster at runtime but the build and unit test suite are clean.
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 82 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 1.26 vet: non-constant format string in Event/EndingEvent calls to EventRecorder8 minutes
- Go not installed in container1 minute
- pkg/controller test fails - needs envtest (etcd/kube-apiserver) binaries not present in container
- test/e2e and test/perf fail - need a real Kubernetes cluster, unavailable in container
- Install time
- 30 minutes
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 4 hit, 2 fixed with no human help
- How the result was proved
- go build ./cmd/velero/ exited 0 producing a 150MB binary; ./tmp/velero --help prints usage text; go test (excluding controller, e2e, perf) reported 98/98 packages passed with 0 FAIL
- Model tokens used
- 531,921
- Exact commit tested
- 8e9f66addf63
- 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.
start = 1790482573
now = 1790484398
minutes = (now - start) / 60
print(f'{minutes:.1f}')\"" in /work/repo
succeeded in 0ms:
30.4
exec
/bin/sh -lc 'export PATH=/tmp/go/bin:$PATH && export GOPATH=/home/runner/go && export GOMODCACHE=/h…
2026-09-27T04:47:44.115167Z ERROR codex_core::session: failed to record rollout items: thread 01a0e…
2026-09-27T04:47:44.115242Z ERROR codex_core::session: failed to record rollout items: thread 01a0e…
tokens used
531,921Replay 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 30.4 minutes.
- 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.
- Hit 4 errors during setup, 2 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 82.00 | 0.13 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/velero)Questions
- Does velero run?
- velero runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 30 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test velero?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 8e9f66addf63. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test velero?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does velero take to install?
- 30.4 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 velero need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing velero?
- 4 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 velero?
- 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.