cloudnative-pg

The most popular Kubernetes Operator for PostgreSQL.

Runssource: GitHubhomepageGoApache-2.0commit c60ac252f566

Go, Apache-2.0 licensed. The project labels itself: automated failover, business continuity, database, database management, devops, disaster recovery, failover and high availability.

cloudnative-pg runs. An Argusic agent installed it in 12 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

CloudNativePG project builds and all unit tests pass with Go 1.27.3; the manager binary accepts --help and version commands, and the kubectl-cnpg plugin binary also responds to --help and version.

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.12 (measured)
recorded runs
2
last tested
stars
9,604
forks
819
open issues
438
watchers
35
size
52 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 cloudnative-pg, 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.

  • Go compiler not installed in container; downloaded Go 1.27.3 tarball manually2 minutes
Install time
12 minutes
Cold machine to finish
17 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
make build produced two binaries (manager, kubectl-cnpg); make test ran 88 test packages and all passed; ./bin/manager version and --help both returned correct output
Model tokens used
163,938
Exact commit tested
c60ac252f566
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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.

 succeeded in 0ms:
1793821404
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 12, "errors": [{"msg": "Go…
exec
/bin/sh -lc "echo '{\"install_succeeded\": true, \"launch_succeeded\": true, \"install_minutes\": 1…
 succeeded in 0ms:
{"install_succeeded": true, "launch_succeeded": true, "install_minutes": 12, "errors": [{"msg": "Go…
tokens used
163,938

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 12 minutes.
  • Recovered from all 1 error 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.
  • Measured 2 times, so the result is not a one-off.

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 Runner2/3Runs100.000.12
Argusic Runner1/3Runs100.000.06

Topics (from GitHub)

automated-failoverbusiness-continuitydatabasedatabase-managementdevopsdisaster-recoveryfailoverhigh-availabilityjson-loggingk8skubectl-pluginkubernetesoperatorpostgrespostgresqlprometheus-exporterreplicationself-healingsqlswitchover

Embed the badge

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

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

Questions

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

Discussion