Drizzle ORM vs Inspektor Gadget

Inspektor Gadget ships a feature release roughly monthly with bugfix releases in between, and the recent line has been steady kernel-side expansion: new gadgets, more eBPF program types, better stack symbolization. v0.55.0 breaks that pattern by adding initial GPU telemetry — a userspace daemon called gpu-ebpf-bridge that publishes GPU data through pinned BPF maps so gadgets can consume it. The rest of the release is the usual widening of eBPF surface plus stability work for high-churn nodes.

Two directions run in parallel. The kernel-side surface keeps growing — SockOps, SkSKB and SkMsg program types, map pinning, non-destructive map iteration, OTel and Python stack symbolization — which makes the tool a more general eBPF runtime rather than a fixed set of gadgets. Meanwhile the output side is becoming opinionated about ecosystems it serves: v0.54.0 taught advise_networkpolicy to emit Cilium NetworkPolicy resources alongside Kubernetes ones. GPU telemetry extends the first direction past the boundary eBPF normally stops at.

The GPU work is explicitly described as an initial design laying groundwork, so expect the next releases to build actual gadgets on top of the bridge rather than to expand it further; the pinned-map plumbing added in the same release is what those gadgets would consume.