mariadb-operator
🦭 Run and operate MariaDB in a cloud native way
Runssource: GitHubhomepageGoMITcommit b04f95f3af57
Go, MIT licensed. The project labels itself: agent skills, agentic ai, ai, backup, cert manager, database, galera and high availability.
mariadb-operator runs. An Argusic agent installed it in 4 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
mariadb-operator binary builds and runs, all 37 unit test suites pass including 222 webhook specs and helm chart template tests
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
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 toolchain not installed2 minutes
- Helm not installed1 minute
- Helm chart dependency not built1 minute
- Install time
- 4 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- make build produced 89MB bin/mariadb-operator; ./bin/mariadb-operator --help printed all commands; make test ran 37 Ginkgo suites, all passed (0 failures, 222/222 webhook specs, all helm tests pass)
- Model tokens used
- 65,755
- Exact commit tested
- b04f95f3af57
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- **`make build`** compiled the 89MB `bin/mariadb-operator` binary successfully - **`mariadb-operator --help`** printed all subcommands and flags - **`make test`** ran 37 Ginkgo suites (222/222 webhook specs + API + pkg + helm test suites) — **a… tokens used 65,755 Everything is done. Here's the summary: - **Go** was not in the container — downloaded and extracted Go 1.23.0 to `/home/runner/go` - **Helm** was not in the container — downloaded Helm 3.16.1 to `/home/runner/linux-amd64` - **Helm dependency** was missing — ran `helm dependency build` in the chart dir - **`make build`** compiled the 89MB `bin/mariadb-operator` binary successfully - **`mariadb-operator --help`** printed all subcommands and flags - **`make test`** ran 37 Ginkgo suites (222/222 webhook specs + API + pkg + helm test suites) — **a…
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.
- Recovered from all 3 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 MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 4 minutes to install, slower than the median of the 127 comparable projects Argusic has measured.
Of the 128 agent-skills projects Argusic has installed and timed, mariadb-operator was the 82nd fastest to reach a running state, and 96 of 128 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 4 minutes after the clone.
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
Topics (from GitHub)
agent-skillsagentic-aiaibackupcert-managerdatabasegalerahigh-availabilitykuberneteskubernetes-operatormariadbmariadb-replicationmysqlopenshiftoperatorprometheus-operators3sqlstoragevolumesnapshots
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mariadb-operator)Questions
- Does mariadb-operator run?
- Yes. mariadb-operator runs. Argusic installed and launched it on a clean machine in 4 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test mariadb-operator?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b04f95f3af57. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mariadb-operator?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mariadb-operator take to install?
- 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 mariadb-operator need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mariadb-operator?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mariadb-operator compare with the alternatives?
- Of the 128 agent-skills projects Argusic has installed and timed, mariadb-operator was the 82nd fastest to reach a running state, and 96 of 128 reached one at all.
- Where is the evidence for mariadb-operator?
- 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.