kubeshark
eBPF-powered network observability for Kubernetes. Indexes L4/L7 traffic with full K8s context, decrypts TLS without keys. Queryable by AI agents via MCP and humans via dashboard.
Runs with mockssource: GitHubhomepageGoApache-2.0commit 35e484c9f1cc
Go, Apache-2.0 licensed. The project labels itself: cloud native, devops, docker, ebpf, golang, grpc, incident response and kubernetes.
kubeshark runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
Go toolchain installed, project builds, binary produces valid output for help and version commands, and all 4 test packages (cmd, config, kubernetes, semver) pass with every subtask succeeding.
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 86 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.
- Install time
- 3 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- go test -v ./... exited 0, 4 packages passed with 0 failures; ./bin/kubeshark --help printed usage for 15 commands; ./bin/kubeshark version printed 0.0.0
- Model tokens used
- 96,254
- Exact commit tested
- 35e484c9f1cc
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
--- PASS: TestGreaterThanComparesNumericComponents/patch_component_with_fewer_digits (0.00s)
--- PASS: TestGreaterThanComparesNumericComponents/lower_major_component (0.00s)
--- PASS: TestGreaterThanComparesNumericComponents/same_version (0.00s)
--- PASS: TestGreaterThanSupportsKubernetesGitVersionPrefix (0.00s)
PASS
ok github.com/kubeshark/kubeshark/semver 0.003s
All tests pass with zero failures. Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3, "er…
tokens used
96,254
All tests pass with zero failures. Here's the final report:
**ARGUSIC_RESULT:** {"install_succeeded": true, "launch_succeeded": true, "install_minutes": 3, "er…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
- Installed in 3 minutes.
- Nothing broke on the way: zero errors between clone and running.
- Licensed Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
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 with mocks | 92.00 | 0.03 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.02 |
Topics (from GitHub)
cloud-nativedevopsdockerebpfgolanggrpcincident-responsekubernetesmcpnetwork-analysisnetwork-engineeringnetwork-observabilitynetwork-securityobservabilitypcaprestroot-cause-analysissniffersrewireshark
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kubeshark)Questions
- Does kubeshark run?
- kubeshark runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test kubeshark?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 35e484c9f1cc. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test kubeshark?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does kubeshark take to install?
- 3 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 kubeshark need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing kubeshark?
- Nothing did, in the recorded run: zero errors between clone and running.
- Where is the evidence for kubeshark?
- 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.