New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vendor: bump tcptracer-bpf #3042
vendor: bump tcptracer-bpf #3042
Conversation
This includes: * an eBPF object built with a newer kernel (4.14) * an increased threshold for guessing offsets, which is necessary for the eBPF tracer to work on Google's Container-Optimized OS (used by GKE)
What was the previous one built with? What do we gain by the change? Any compatibility issues? |
I started a 1.8.6 GKE cluster and deployed scope built with this PR to it. It seems to work fine:
You can try my image:
|
We were building with whatever Fedora 25 has. Currently it's 4.13.16.
The change is there because weaveworks/tcptracer-bpf#52 got merged, which updates the docker image used to build tcptracer-bpf to Fedora 26. We might get better code if the version of clang in Fedora 26 is newer, but nothing else.
Not that I know of, since we use the offset guessing code it shouldn't matter what version is used to build the eBPF object nor what version the code runs on. |
I have tested this in my existing GKE cluster, and it all works fine. |
This includes:
the eBPF tracer to work on Google's Container-Optimized OS (used by
GKE)
Fixes #2796