Some problems with Diagnosis
- Dominant language
- Go
- Stars
- 698
- Forks
- 91
- Avg merge
- 32m
- Merged PRs (30d)
- 1
Description
1. Capture:
When Capturing in pods like kubeskoop's "pod controller" , meet this error: "failed to run command: pod not found on nettop cache".
When Capturing in pods like kubeskoop's "pod agent", it meet this error: "failed to upload task result", and "pod controller" seems to crash and reload.
2. Connectivity Diagnosis:
How could I submit args like "--network-plugin", when auto-detection failed on web console?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the two Capture failures in the pod controller and pod agent, then inspect how the web console handles Connectivity Diagnosis when auto-detection fails. Done should include successful capture without the cache, upload, or controller reload errors, plus a documented or working way to submit the --network-plugin argument.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- networking, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100