docs: integration templates for the remaining loader archetypes#99
Merged
Conversation
Adds copy-paste starting points for Go (libbpfgo, ebpf-go), Rust/Aya, and an in-process pre-load gate, alongside the existing OCI gadget template, plus an index that leads with the wedge: bring your own loader, there is nothing to maintain. Templates convert where prose does not. Adoption so far has needed bespoke per-project work; these let a maintainer copy one file instead of reading a README and inferring the rest. Each pins the action by commit SHA (a release-matching SHA resolves to prebuilt, checksum-verified binaries, so no toolchain is needed) and defaults to the vendor-kernel quirk library, where version numbers stop predicting behaviour. Signed-off-by: ErenAri <erenari27@gmail.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
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.
Completes the template set. A maintainer can now copy one file rather than read a README and infer the rest — which is the difference between adoption that scales and adoption that needs six weeks of bespoke work per project.
go-loader-compatibility.ymlrust-aya-compatibility.ymllibrary-gate.go.mdinspektor-gadget-compatibility.yml(existing)The framing
All four lead with the same idea, because it is the thing that actually unblocked the falcosecurity/libs merge: bring your own loader, there is nothing to maintain. No manifest means no second description of your program to drift out of sync.
The Rust template calls out something worth knowing: Aya is a pure-Rust loader, not a libbpf wrapper, so a "loads under libbpf" result does not transfer. Same for ebpf-go. That is the argument for validating the binary you actually ship rather than re-loading the object with someone else's loader.
Details