k8s
Platform In a Box!
Runssource: GitHubhomepageShellMITcommit b36530262a20
Shell, MIT licensed. The project labels itself: argocd, autoscaling, cert manager, ci cd, elasticsearch, envoy, envoy gateway and high availability.
k8s runs. An Argusic agent installed it in 42 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
All 13 Helm charts render and pass lint; 47 container images were scanned for CRITICAL vulnerabilities with no failures; Checkov policy scanning passes on all first-party chart templates with only expected warnings from Kyverno's upstream dependency.
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.
- scripts/scan.sh debug() function uses (( DEBUG )) arithmetic which returns exit code 1 with set -e when DEBUG=0, killing the entire scan silently13 minutes
- Missing required binaries (helm, yq, trivy, checkov)6 minutes
- cert-manager Helm dependency resolution failed - repo mismatch against Chart.yaml versions v1.16.3 and reflector 7.1.2623 minutes
- Missing helm repos for eck-operator, elastic-stack, envoy-gateway, external-dns, jaeger, kyverno, redis, sealed-secrets, valkey2 minutes
- checkov scan reports 4 failures for kyverno chart (CPU/memory limits on upstream dependency templates)
- Install time
- 42 minutes
- Cold machine to finish
- 44 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- scripts/scan.sh lint --all exited 0 (13 charts, 48 values files); scripts/scan.sh trivy --all exited 0 (47 images scanned, 0 CRITICAL failures); scripts/scan.sh checkov --all exited 1 with 4 expected kyverno policy warnings (0 failures in our charts); helm template succeeded for all 13 charts
- Model tokens used
- 293,860
- Exact commit tested
- b36530262a20
- 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.
=== Time check === Started: ~04:17 UTC, Finished: ~04:59 UTC All three scan steps completed. Here's the final report: **Lint**: 13 charts, 48 values files, 0 failures — **pass** **Trivy**: 47 unique container images scanned, 0 failures by CRITICAL severity threshold — **pass** **Checkov**: 48 values/helm scans, 4 expected policy warnings in kyverno upstream templates (CPU/me… tokens used 293,860 All three scan steps completed. Here's the final report: **Lint**: 13 charts, 48 values files, 0 failures — **pass** **Trivy**: 47 unique container images scanned, 0 failures by CRITICAL severity threshold — **pass** **Checkov**: 48 values/helm scans, 4 expected policy warnings in kyverno upstream templates (CPU/me…
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 42 minutes.
- Recovered from all 5 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.
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)
argocdautoscalingcert-managerci-cdelasticsearchenvoyenvoy-gatewayhigh-availabilityjaegerkuberneteskyvernomonitoringnginx-ingress-controllerplatform-engineeringprometheusprometheus-clusterredissealed-secretsthanos
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/k8s)Questions
- Does k8s run?
- Yes. k8s runs. Argusic installed and launched it on a clean machine in 42 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test k8s?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit b36530262a20. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test k8s?
- The run that produced this verdict cost $0.34: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does k8s take to install?
- 42 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 k8s need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing k8s?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for k8s?
- 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.