Add jq, tcpdump, and iputils to whereami container image about kubernetes-engine-samples HOT 7 CLOSED

Let's chat about this further. Thinking about the Unix philosophy of "do one thing and do it well". whereami's one thing is location reporting/diagnostics for K8s pods. netshoot's one thing is K8s network troubleshooting. I'm thinking we should leverage netshoot for its superpower of aggregating a bunch of useful tools instead of trying to replicate it.

from kubernetes-engine-samples.

I checked with @mark-church and we can close this

from kubernetes-engine-samples.

another thing - we can use kubectl port-forward at some pod + local installations of tools like jq to troubleshoot for some situations.

from kubernetes-engine-samples.

@theemadnes I'd like to open this issue back up. I want to use whereami in the Cloud DNS docs (https://cloud.devsite.corp.google.com/kubernetes-engine/docs/how-to/cloud-dns) but I can't because it has no local networking troubleshooting tools. I think the original request was misunderstood because the purpose was not to use whereami as a troubleshooting container, but rather it should have the minimum amount of tools to demonstrate different networking things. None of the tools that I need to demonstrate DNS are in the image:

kubectl exec -it whereami -- sh
$ dig
sh: 3: dig: not found
$ drill
sh: 4: drill: not found
$ nslookup
sh: 5: nslookup: not found
$ exit

The following tools would be useful to have:

• dig or drill
• ping
• git
• openssl (although I could live without it)
• jq
• iputils (I think this is for the "ip" command)

from kubernetes-engine-samples.

ok that makes sense. can you set up a little time to chat about it? want to figure out if we make it default or add a companion "whereami + utils" image, and also walk through figuring out if we need to modify any permissions needed for the pod.

from kubernetes-engine-samples.

switching this to just include curl per request by @mark-church

from kubernetes-engine-samples.

hi @theemadnes!
Are there any more action items that you and @mark-church wanted to implement through this issue?
If not we can close this issue

from kubernetes-engine-samples.