solr-operator

Official Kubernetes operator for Apache Solr

Runssource: GitHubhomepageGoApache-2.0commit ed5c5c7d28a4

Go, Apache-2.0 licensed. The project labels itself: aks, aws, azure, controller, crd, eks, gcp and gke.

solr-operator runs. An Argusic agent installed it in 10.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.

Go 1.27.3 installed, all dependencies resolved, project builds cleanly, and 105 unit tests (76 Ginkgo controller specs + 29 Go util tests) all pass using downloaded kubebuilder envtest assets (k8s 1.36.0). E2E tests skipped as they require a real Kubernetes cluster.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.09 (measured)
recorded runs
1
last tested
stars
285
forks
154
open issues
67
watchers
43
size
5 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 solr-operator, 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.

  • kubebuilder envtest binaries (etcd, kube-apiserver) not found at /usr/local/kubebuilder/bin/6 minutes
  • Go 1.27.3 not installed on system1.5 minutes
Install time
11 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 ./api/... ./controllers/... with KUBEBUILDER_ASSETS=/work/repo/bin/k8s/1.36.0-linux-amd64: 76 controller specs passed, 0 failed; controllers/util tests: 29 passed, 0 failed (exit 0); go build ./... and go build . both exited 0; binary /tmp/solr-operator --help printed version v0.10.0-prerelease, Go 1.27.3
Model tokens used
251,118
Exact commit tested
ed5c5c7d28a4
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 attempt that decided the verdict above. 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.

exec
/bin/sh -lc 'echo "scale=2; (1793010471 - 1793009820) / 60" | bc' in /work/repo
 exited 127 in 0ms:
/bin/sh: 1: bc: not found
exec
/bin/sh -lc 'python3 -c "print(round((1793010471 - 1793009820)/60, 1))"' in /work/repo
 succeeded in 0ms:
10.8
So total elapsed time is ~10.8 minutes. Here's the final report:
tokens used
251,118
So total elapsed time is ~10.8 minutes. Here's the final report:

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 10.8 minutes.
  • Recovered from all 2 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.

What did not, or is not known

  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

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 Runner1/3Runs100.000.09

Topics (from GitHub)

aksawsazurecontrollercrdeksgcpgkegolanginformation-retrievalkuberneteslucenenosqloperatorsearchsearch-enginesolr

Embed the badge

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

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

Questions

Does solr-operator run?
Yes. solr-operator runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test solr-operator?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit ed5c5c7d28a4. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test solr-operator?
The run that produced this verdict cost $0.09: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does solr-operator take to install?
10.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 solr-operator need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing solr-operator?
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 solr-operator?
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.

Discussion