Skip to content

Move away from bpf2go #219

Description

@aerosouund

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or requestpriority/P3Low: refactor, cleanup or speculative

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions