When you run setup.sh it pulls tools to help with the various debugging methods. Often these tools are compiled and packaged for a single kernel version. Unfortunately, the debian repos that the runtime containers are pointed at can be missing packages for the kernel you happen to be running on. At least kernel versions 4.19 and 4.9 appear to work out of the box.
This document contains information about how to get the debug tooling working on kernels that do not immediately work. Some of these techniques may be dangerous or provide inconsistent results.
A setup script has been provided for 4.15. Note that it uses a snapshot of the unstable repo from 2018 to find 4.15 tooling and linux headers.
echo deb [check-valid-until=no] http://snapshot.debian.org/archive/debian/20180222 sid main contrib >> /etc/apt/sources.list
Using this technique everything except dynamic tracing seems to work.
Similar to 4.15
echo deb [check-valid-until=no] http://snapshot.debian.org/archive/debian/20180222 sid main contrib >> /etc/apt/sources.list
apt-get update
apt-get install linux-tools-4.14
After running setup.sh run the following to install the correct version of perf.
apt-get install linux-perf-4.9
Currently setup.sh attempts to pull the appropriate Linux headers. I believe this will only be successful in a small number of scenarios in which the container repos happen to have the appropriate headers for the host. Commented out lines have been added to dynamic-tracing.yaml that successfully mount Linux headers in GKE on Ubuntu nodes and allow bpf/bcc dynamic tracing. With additional testing this may become the preferred method.