Debugging tools more easily available in compute pods and VMs

[cloneable]

Problem description / Motivation

Debugging tools missing in compute VMs and not easily installable when VM is at memory limit. And because pod uses Alpine and the VM Debian we can't simply copy tools and libs from the pod into the VM.

Feature idea(s) / DoD

During INC-415 it would have helped a lot to have network debugging tools readily available in at least the pod and possibly in the VM.

Implementation ideas

I understand we don't want to have too many things exposed in the VM by default, so I would be good if one can easily install debug tooling ad-hoc. This could be a tarball in the pod that unpacked inside the VM when a script in the pod is run.

Ideally, we would have a pre-built image used with kubectl debug containing everything we need.

[sharnoff]

From @kelvich: fixing #1304 might provide another route for this issue

[kelvich]

that was helpful:

apt update
apt install -y tcpdump screen iproute2 dnsutils iputils-ping lsof strace

[cloneable]

Right, I should have mentioned that sometimes it's not possible to install tools when VM is too loaded:

$ apt install iproute2 tcpdump
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  dbus libapparmor1 libatm1 libbpf0 libbsd0 libcap2 libcap2-bin libdbus-1-3 libmd0 libmnl0 libpam-cap libpcap0.8
  libxtables12
Suggested packages:
  default-dbus-session-bus | dbus-session-bus iproute2-doc apparmor
The following NEW packages will be installed:
  dbus iproute2 libapparmor1 libatm1 libbpf0 libbsd0 libcap2 libcap2-bin libdbus-1-3 libmd0 libmnl0 libpam-cap libpcap0.8
  libxtables12 tcpdump
0 upgraded, 15 newly installed, 0 to remove and 10 not upgraded.
Need to get 0 B/2556 kB of archives.
After this operation, 7033 kB of additional disk space will be used.
Do you want to continue? [Y/n]
FATAL -> Failed to fork.