eiffel-fl

It seems AKS default OS SKU was changed from Ubuntu 18.04 to Ubuntu 22.04, so this bug does not occur on this version of Ubuntu as the kernel contains the...

The patch was [backported](https://lists.ubuntu.com/archives/kernel-team/2022-September/133404.html) to 5.4 kernel. So, when the next 5.4 will be released this bug should not occur anymore.

I am not really sure regarding the root cause: 1. On one side, the [commit](https://github.com/torvalds/linux/commit/c4f6699dfcb8558d138fe838f741b2c10f416cf9) introducing raw tracepoint was merged in 4.17. 2. On the other side, the [commit](https://github.com/torvalds/linux/commit/f1b9509c2fb0ef4db8d22dac9aef8e856a5d81f6) which...

[This bcc's comment](https://github.com/iovisor/bcc/issues/4231#issue-1367894518) confirms the `tp_btf` are only available for kernel 5.5. Nonetheless, `cilium/ebpf` uses raw tracepoint as shown by this error message: ``` Gadget biolatency: falling back to standard...

In https://github.com/inspektor-gadget/inspektor-gadget/compare/main...francis/biolatency-raw-tp, I converted `biolatency` to use raw tracepoint rather than BTF ones, it then fixed the problem. Nonetheless, a better solution, which permits using BTF tracepoint when available and...

When trying https://github.com/inspektor-gadget/inspektor-gadget/commit/78d2c420d220770377c67dcff2060825175efdf1, I am getting the following error: ``` time="2022-11-07T21:04:54Z" level=info msg="Gadget biolatency: falling back to standard tracer. CO-RE tracer failed: failed to load ebpf program: field IgProfioDone: program...

Should we really do this? More particularly, what are the guarantees we offer when someone uses different versions of the CLI and server?

> None so far. I suppose this is something we'll be considering once we approach to v1.0. If we permit users to use different versions for the CLI and the...

> after an update of the CLI with kubectl krew upgrade gadget. I missed this point and Mauricio did well highlighting it. With this particular case and the others you...

> krew only cares about updating the gadget binary and IMO it'll be very difficult to implement logic to run extra steps when updating a binary I checked [`krew` code](https://github.com/kubernetes-sigs/krew/blob/bc201bda0c9f2956d608c9d7d49702fa2fba1a82/internal/installation/upgrade.go#L32)...