bpf

Seems we have some language features not fully documented (like bitshift operators in #1322).

Would be good to go through language grammar and make sure everything is in the reference guide.

Currently we have just one type of docs which are "reference" documentation. We should add a "how-to/tutorials" section with goal-driven content. We can start by drawing already available content:

https://blog.aquasec.com/kubernetes-runtime-security-ebpf
https://blog.aquasec.com/tracee-runtime-malware-alerts-aqua-postee
https://blog.aquasec.com/runtime-security-tracee-rules
https://github.co

At the moment of writing this issue, kubectl trace only supports X86-64 as target architecture.

The tool should be able to schedule bpftrace programs against all the architectures supported by bpftrace, that are X86-64 and arm64 (aarch64) see the Cmake definition.

To achieve that we n

kinvolk/inspektor-gadget#163 introduced support for a new hook mode based on NRI (Node Resource Interface). Currently this mode only works if the user explicitly pass the --hook-mode=nri option and it's not considered when --hook-mode=auto is used.

Inspektor Gadget should detect if containerd v1.5+ is used as runtime and set HOOK_MODE="podinformer" in the followin

When we declare a constant variable that has an initializer, e.g. bool x constant = 0 < 2, we evaluate the actual constant value in compiler time. Currently, there is no support to evaluate constants in comparisons, so the aforementioned example is evaluated in run time.

We need to calculate comparisons with constants during compilation. The eval_const_number function should become `eval_co

Feature Request

Short Description

Currently, the GRPC server port [is a configuration](https://github.com/kubearmor/KubeArmor/blob/bf39613c0c01e986d3e77d2f46a59c526cbf5907/KubeArmor/config/config.go#L79) and the default value is 32767.
This works fine on kubearmor in

Can we get some performance comparison between polycube and using standard linux facilities (NAT, iptables, etc.)?

CPU usage, PPS, latencies, etc.

https://github.com/aquasecurity/libbpfgo/blob/main/helpers/osinfo.go seems to be untested. It would be helpful to add some unit tests to cover certain scenarios.

nhi currently supports only systemd