What problem does this solve?
bpf2go stifles us in terms of repo structure, the project's bpf layer is growing and is becoming more intermingled in terms of functions and variables used. at one point it would be beneficial to have a bespoke solution
Proposed change
Alternatives considered
No response.
Additional context
No response.
Delivery planning
Outcome: Operate at scale. Priority: P3.
Require a reproducible build/tooling blocker and measured benefit before replacing bpf2go. Preserve pinned generation, verifier loading and artifact drift checks. This is not a prerequisite for CIDR/prefix feature delivery.
Follow the repository build/test, kind behavior, documentation and redaction requirements. Acceptance must distinguish prevention from observation.
What problem does this solve?
bpf2go stifles us in terms of repo structure, the project's bpf layer is growing and is becoming more intermingled in terms of functions and variables used. at one point it would be beneficial to have a bespoke solution
Proposed change
Alternatives considered
No response.
Additional context
No response.
Delivery planning
Outcome: Operate at scale. Priority: P3.
Require a reproducible build/tooling blocker and measured benefit before replacing bpf2go. Preserve pinned generation, verifier loading and artifact drift checks. This is not a prerequisite for CIDR/prefix feature delivery.
Follow the repository build/test, kind behavior, documentation and redaction requirements. Acceptance must distinguish prevention from observation.