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

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions