[neo2006]

Thank you! Not really, the controller is not doing dataplane per-say, it only pushes eBPF programs to the kernel for the relevant apps/cgroups so that could be considered control-plane. The full data-plane run in eBPF.

[captn3m0]

1. Code that manages the Kubernetes manifests. This doesn’t need to live alongside your actual app.

2. Code that does injection in eBPF and needs to live along your app.

From my understanding from the README and helm chart, these are both in the daemonset.

[neo2006]

Actually we have 2 applications along those boundaries you described. a webhook app that manage kubernetes manifest and another to inject the ebpf code and manage the ebpf maps.

Thank you for the feedback though! I think we need to clarify the doc to make that separation clear. I will open an issue for that and we will work on it.