konflux-ci
Trusted builds made easy! A cloud-native software factory for building, testing, and releasing trusted software artifacts
Runssource: GitHubhomepageGoApache-2.0commit 507449b62240
Go, Apache-2.0 licensed. The project labels itself: ai, ci cd, cloud native, go, kubernetes, oci, sbom and sigstore.
konflux-ci runs. An Argusic agent installed it in 14 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Operator builds and lints clean; full unit/envtest suite passes; the built manager ran against a live kube-apiserver, answered /healthz 200, created all sub-CRs and namespaces from a Konflux CR, and reported component conditions; operand pods cannot schedule because this container has no container runtime.
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.
- container lacked Go toolchain; operator/go.mod requires go 1.26.03 minutes
- bin/manager startup blocked because cert-manager CRDs absent (informers fail: no matches for kind Certificate)2 minutes
- make install failed: kubectl not found on PATH1 minute
- operand pods cannot run: no container runtime/scheduler in this container (cert-manager-webhook unreachable, ApplyFailed on Certificate; Ready=False ComponentsNotReady)1 minute
- Install time
- 14 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- make test exited 0 (38/38 packages ok); make lint 0 issues; ./bin/manager started 16 controllers and GET /healthz returned 200 'ok'; Konflux CR reconciled into 12 sub-CRs and namespaces with status CertManagerAvailable=True, rbac.Ready=True
- Model tokens used
- 532,729
- Exact commit tested
- 507449b62240
- 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.
- Noted root cause of one diagnosis: initial `Bad substitution` was my own `${PIPESTATUS}` bashism …
**Launch / test**
- Installed envtest K8s 1.37.0 binaries via `make test`'s `setup-envtest`.
- `make test` exited 0: 38/38 packages `ok` (e.g. `internal/controller/ui 102.651s`, `segmentbridge…
- Stood up a real single-node control plane using the bundled envtest `etcd`/`kube-apiserver` (own …
- Logged `Konflux Operator {"version": "0.0.1", "gitCommit": "507449b6..."}`, "Starting Controlle…
- Applied sample `config/samples/konflux_v1alpha1_konflux.yaml`: the operator created all 12 sub-…
- The one runtime error logged by the operator itself: "failed to reconcile operator metrics scrape…
- Repo working tree remained clean (only gitignored build artifacts).
**Constraints encountered**
- No `docker`/`podman`/`kind`/container runtime in the container, so operand deployments can't sche…
Now the one-line result, as a single JSON object on the same line: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 4 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
- Took 14 minutes to install, slower than the median of the 223 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 224 ai projects Argusic has installed and timed, konflux-ci was the 164th fastest to reach a running state, and 146 of 224 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.
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)
aici-cdcloud-nativegokubernetesocisbomsigstoreslsasupply-chainsupply-chain-securitytekton
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/konflux-ci)Questions
- Does konflux-ci run?
- Yes. konflux-ci runs. Argusic installed and launched it on a clean machine in 14 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test konflux-ci?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 507449b62240. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test konflux-ci?
- The run that produced this verdict cost $0.14: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does konflux-ci take to install?
- 14 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 konflux-ci need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing konflux-ci?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does konflux-ci compare with the alternatives?
- Of the 224 ai projects Argusic has installed and timed, konflux-ci was the 164th fastest to reach a running state, and 146 of 224 reached one at all.
- Where is the evidence for konflux-ci?
- 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.