chore(deps): align node-agent main with the three-forks pin (fixes build)#28
Merged
chore(deps): align node-agent main with the three-forks pin (fixes build)#28
Conversation
- inspektor-gadget → k8sstormcenter/inspektor-gadget (carries 6 matthyx patches atop upstream main: datasource pooling, disable kallsyms, dummy LostSampleCount, host-network flag, oras-target release, trace_capabilities map-size reduction). - kubescape/storage → k8sstormcenter/storage (feat/zero-alloc-wildcards, with syft downgraded to v1.32.0 for node-agent compatibility). - Drops matthyx/inspektor-gadget replace (stale, patches now carried on our own fork instead). - Drops direct github.com/moby/moby v28.5.2+incompatible pin (the new IG pulls in github.com/moby/moby/client v0.3.0 only; the old pin caused an ambiguous-import when both modules were present). Full unit test run: 50 packages green; 4 failures isolated to pkg/containerwatcher/v2/tracers are environmental (eBPF MEMLOCK limit in OrbStack), not code failures. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
kubescape/k8s-interface renamed KindMetadataKey → RelatedKindMetadataKey (and Name / Namespace variants) between v0.0.204 and v0.0.206. Our Test_28 (UserDefinedNetworkNeighborhood) and Test_30 (TamperedSigned Profiles) still referenced the old names, so with the v0.0.206 helpers pulled in by upstream go.mod the full component_test.go failed to compile. Unit tests pass with -short because they skip these full- cluster tests. 5 occurrences renamed. No semantic change. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
entlein
pushed a commit
that referenced
this pull request
Apr 26, 2026
Brings in 9 upstream commits: rule-manager hot-path perf (kubescape#794), CEL constant folding + set membership optimizers (kubescape#789), iouring CO-RE relocation fix for kernel 6.8+ (kubescape#741), go-ntlmssp v0.1.1 bump (kubescape#790), and matthyx fork validation (kubescape#786). Conflict resolution: - go.mod replaces: kept our k8sstormcenter/{inspektor-gadget,storage} pin (the three-forks alignment from #28); dropped upstream's experimental matthyx/inspektor-gadget and matthyx/ebpf replaces (those are temporary upstream test forks for NAUT-1252 memory work, not relevant to our fork stack). - go.sum: regenerated via go mod tidy. Build clean. Unit suite: 92 packages pass; only TestRandomxFields fails (stale tracers.tar — explicitly ignored per prior decision). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cherry-picks two commits from `feat/zero-alloc-wildcards` (node-agent's last known-green state, 2026-04-22) onto `main`:
f4232ec — `chore(deps): pin node-agent to our three forks`
d8489b4 — `tests(component): rename to Related{Kind,Name,Namespace}MetadataKey`
Why main is broken today
The main-branch build (cascade from storage#16 merge, run 24889813076) failed in three distinct ways that all resolve under the same three-forks alignment:
Verification
Local build (same target the CI Dockerfile uses):
```
go version go1.25.8
go build -o /tmp/na-fixed ./cmd/main.go # OK — 273MB binary produced
```
Out of scope
The storage pin on this branch points at `k8sstormcenter/storage v0.0.240-0.20260422124404-e030700404ef` (the feat/zero-alloc-wildcards tip). The `upstream-pr/analyzer-zero-alloc` branch pins a different storage SHA (897fcbcd) which has syft bumped to v1.42.3 — that rewrites the same three issues back into the graph. The regression test against upstream-pr will still fail until that storage pin gets syft downgraded to v1.32.0; noted as a separate follow-up (needs a human commit per the upstream-pr workflow).
Test plan