k8spacket

Hi @marton-szabo-hotstar Getting it from DNS queries is not the best solution regarding the cloud world. f.e. calling `nslookup` for IP of domain `ebpf.io`: ``` nslookup ebpf.io ... Name: ebpf.io...

Hi @marton-szabo-hotstar I'm going to close this issue. Described solution will be realize in ticket: https://github.com/k8spacket/k8spacket/issues/82

https://github.com/k8spacket/k8spacket/issues/82#issuecomment-2474172843

Hi @bonapeti k8spacket uses the Golang plugin approach (https://pkg.go.dev/plugin) where `nodegraph` and `tls-parser` are built as plugins and provided to the k8spacket base application from the outside. - plugins loader:...

Hi @bonapeti k8spacket no longer uses go-plugins since version 2.1.0 - https://github.com/k8spacket/k8spacket/releases/tag/v2.1.0 I'm going to close that issue.

Hi @alexandersperling The message: `Cannot find plugin ...` is expected here because: - nodegraph plugin implements only the `TCPConsumerPlugin` symbol, so the message informs about missing another symbol `TLSConsumerPlugin` -...

Additionally, what version of Linux kernel is there on your AmazonLinux VMs? Remember about the limitation kernel version >= 5.8

Ok, my fault. The path mounted from the node should be `/sys/kernel/debug/tracing`, but the container should see it on the path: `/sys/kernel/tracing` It should look like: ``` spec: template: spec:...

Of course. It is a great idea to add `volumes` and `volumeMounts` to `values.yaml`.

Merged To install the new version: ``` helm repo update k8spacket helm install k8spacket --namespace k8spacket k8spacket/k8spacket --create-namespace ``` Thanks @alexandersperling 👏