kiali
Kiali project, observability for the Istio service mesh
Runssource: GitHubhomepageGoApache-2.0commit da2138100483
Go, Apache-2.0 licensed. The project labels itself: istio, management, observability, openshift and service mesh.
kiali runs. An Argusic agent installed it in 29 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Kiali backend binary builds and runs, all 121 Go unit test packages pass, and the React frontend UI builds successfully, but a Kubernetes cluster with Istio is required for full integration testing.
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.
- Node.js 18 lacks corepack support and yarn 4 at packageManager version11 minutes
- Go 1.26.3 required but not installed in environment3 minutes
- yarn 4.12.0 (packageManager field) is not published to npm; only yarn 1.22.22 and 2.4.3 available3 minutes
- npm install --legacy-peer-deps with Node 18 failed on peer dependency conflict (monaco-editor)
- Install time
- 29 minutes
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- Kiali binary built and responded to --help with 'Kiali is the console for Istio service mesh'; go test -tags exclude_frontend passed on all 121 packages (log, config, server, models, routing, business, prometheus, graph, handlers, tracing, util, cache, istio, store, controller, ai, etc.) with 0 failures; frontend rsbuild build completed producing index.html, CSS, and JS bundles; server startup initialized all subsystems and exited only on missing kubeconfig (no k8s cluster available in container)
- Model tokens used
- 223,976
- Exact commit tested
- da2138100483
- 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.
=== DONE === Now I have all the data needed for the final report. 2026-10-01T01:48:19.229546Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-10-01T01:48:19.229579Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-10-01T01:48:19.229592Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-10-01T01:48:19.229623Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-10-01T01:48:19.229640Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-10-01T01:48:19.229649Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-10-01T01:48:19.229658Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… tokens used 223,976 Now I have all the data needed for 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 29 minutes.
- 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
- 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
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kiali)Questions
- Does kiali run?
- Yes. kiali runs. Argusic installed and launched it on a clean machine in 29 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test kiali?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit da2138100483. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test kiali?
- The run that produced this verdict cost $0.24: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does kiali take to install?
- 29 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 kiali need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing kiali?
- 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.
- Where is the evidence for kiali?
- 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.