Summary
We need a simple release gate to make sure our eBPF agent is safe to deploy across supported kernels and distros.
We should not try to support “all kernels”.
We should define a small supported matrix and test those continuously.
Goal
Build a CI pipeline that verifies:
- the eBPF object can load
- required features exist on the host
- attach/detach works cleanly
- the agent does not leave broken state behind
- basic runtime overhead is acceptable
- a report is generated for each kernel lane
What we need:
self-hosted runners for each kernel/distro lane we want to validate
optionally ARC or a runner pool if we want to scale this later
Initial scope
Support a small matrix first:
Ubuntu LTS
Debian stable
RHEL/Rocky
Amazon Linux
x86_64 first
arm64 later
What to test
TBD
Summary
We need a simple release gate to make sure our eBPF agent is safe to deploy across supported kernels and distros.
We should not try to support “all kernels”.
We should define a small supported matrix and test those continuously.
Goal
Build a CI pipeline that verifies:
What we need:
self-hosted runners for each kernel/distro lane we want to validate
optionally ARC or a runner pool if we want to scale this later
Initial scope
Support a small matrix first:
Ubuntu LTS
Debian stable
RHEL/Rocky
Amazon Linux
x86_64 first
arm64 later
What to test
TBD