k8spacket
k8spacket - collects TCP traffic and TLS connection metadata in the Kubernetes cluster using eBPF and visualizes in Grafana
Runssource: GitHubGoApache-2.0commit 76c2d1de1ac4
Go, Apache-2.0 licensed. The project labels itself: bpf2go, cilium, ebpf, ebpf programs, ebpf tc, grafana, k8spacket and metrics.
k8spacket runs. An Argusic agent installed it in 6 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The k8spacket Go project builds successfully with CGO_ENABLED=0 into a static binary; all 31 test packages pass (26 testable packages across cmd, internal/broker, internal/ebpf/*, internal/modules/*, internal/thirdparty/*); the binary starts and serves HTTP /metrics on port 6676 but eBPF program loading is blocked due to missing kernel capabilities in this container.
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 75 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 compiler not found in container1 minute
- Install time
- 6 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- K8S_PACKET_K8S_RESOURCES_DISABLED=true go test -count=1 ./... exited 0 with 31 packages all PASS, zero failures; also verified CGO_ENABLED=0 go build exits 0 producing a 44MB static binary
- Model tokens used
- 358,409
- Exact commit tested
- 76c2d1de1ac4
- 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 2, 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.
] } All 31 test packages pass with zero failures. Let me compile the final report. **Time spent:** started at ~16:31 UTC, now ~16:37 UTC. That's about 6 minutes. exec /bin/sh -lc 'date -u' in /work/repo succeeded in 0ms: Sat Oct 10 16:37:22 UTC 2026 All done. Here is the final report: tokens used 358,409 All done. Here is 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 6 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.
- A quick evaluation: it was running 6 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.06 | |
| Argusic Runner | 1/3 | Did not run | 50.00 | 0.05 |
Topics (from GitHub)
bpf2gociliumebpfebpf-programsebpf-tcgrafanak8spacketmetricso11yobservabilitypacketsniffingprometheustcptlsvisualization
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/k8spacket)Questions
- Does k8spacket run?
- Yes. k8spacket runs. Argusic installed and launched it on a clean machine in 6 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test k8spacket?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 76c2d1de1ac4. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test k8spacket?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does k8spacket take to install?
- 6 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 k8spacket need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing k8spacket?
- 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 k8spacket?
- 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.