Closed LucaGuerra closed 10 months ago
/assign @FedeDP /assign @LucaGuerra
Still missing:
modern-bpf
will become modern-ebpf
) and eventually other Falco config changesunix.lsmod/insmod
etc etc instead of exec.Command
to reduce exec.Command usagesI'd like to tag a 0.7.0-alpha once https://github.com/falcosecurity/falco/pull/2413 is merged and needed changes land in falcoctl, to be able to test Falco with the new driver-loader.
I'd like to tag a 0.7.0-alpha once falcosecurity/falco#2413 is merged and needed changes land in falcoctl, to be able to test Falco with the new driver-loader.
I'll take a look at https://github.com/falcosecurity/falco/pull/2413 soon :+1:
IMHO we can close this one; Falco master now ships the new driver loader, and tests are ongoing. Not much development left (except for fixing bugs if they happen). /close
@FedeDP: Closing this issue.
What would you like to be added:
According to this proposal: https://github.com/falcosecurity/falco/blob/master/proposals/20221129-artifacts-distribution.md#deprecate-falco-driver-loader we need a new home for the Falco driver loader. This issue acts as a basic requirement specification for this and as a place for discussion. The issue will be updated with more details as it's being developed.
This issue covers feature parity with the driver loader script. The main required features are:
In addition, the design should allow for other projects using the Falco libs to use falcoctl or import it into their own Go-based tooling, meaning that their strategy to download and build prebuilt could be a little different and the design should still allow for that to work. In addition, it should be easier for contributors to add support for their own favorite distribution, since it has proven to be a bit hard to do the same in the bash script.
Why is this needed:
https://github.com/falcosecurity/falco/blob/master/proposals/20221129-artifacts-distribution.md#deprecate-falco-driver-loader