← all publishers

inspektor-gadget

@inspektor-gadget source repo

Report this profile Claim this profile

• 2 skills
• 0 followers
• 22 hours ago last updated

1. ▌
   Linux Troubleshooting · inspektor-gadget bundle

   Debug a single Linux host, VM, or container runtime at the kernel level with Inspektor Gadget via the standalone `ig` binary — no Kubernetes required. Use when something on a bare host, edge node, CI runner, or Docker/containerd/CRI-O box is failing and logs aren't enough: DNS or TCP failures, connection resets / retransmits / drops, processes exiting or being killed (OOM/signal), failed or missing file opens, permission / capability / seccomp / LSM denials, slow disk or file I/O, or "which process made this syscall / connection". Traces real kernel events with eBPF; enriches with container name/runtime when a runtime is present. Read-only. Not for Kubernetes clusters (use kubernetes-troubleshooting for `kubectl gadget`), plain application logs, or metrics dashboards.
   0
   installs
2. ▌
   Kubernetes Troubleshooting · inspektor-gadget bundle

   Debug live Kubernetes workloads at the kernel level with Inspektor Gadget via `kubectl gadget run`. Use when a pod or Service is misbehaving and application logs are not enough: DNS resolution failures or slow lookups, TCP connection resets / retransmits / drops / refused connections, CrashLoopBackOff, "no such file or directory", permission / capability / seccomp / LSM denials, OOMKilled, unexpected process execs, slow disk or file I/O, or "which pod/process made this syscall / connection / DNS query". Traces real kernel events with eBPF, auto-enriched with pod / namespace / container / node. Read-only, no workload changes. Not for plain application logs, long-term metrics dashboards, or editing cluster state.
   0
   installs