netshoot VS podinfo

Now, let's use netshoot, a Docker image equipped with a set of networking troubleshooting tools that can be used for Docker networking.

nicolaka/netshoot for sure. having a preloaded array of networking troubleshooting tools in an image for kubernetes debugging is a godsend.

First off, it seems like getting tcpdump or Wireshark to capture from the container network and dumping to a file will take some extra steps. (A lot of blog posts seem to recommend this Github project - https://github.com/nicolaka/netshoot)

Some hints how to debug such problems in the future: 1. ufw drops/rejections are logged (use dmesg to view them) 2. wireshark shows all connection attempts, even those that are blocked by firewall 3. ss or netstat shows if the server is actually listening for connections 4. netshoot allows to enter docker container network namespace and do pings, curl or telnet from there

I would recommend setting up a simple Kubernetes cluster (maybe using KinD, minikube, or something similar) and getting to know how it works (you could try deploying something like Kuard or Podinfo or deploy one of your own containerized apps to Kubernetes).

Podinfo does something very similar while coming with alot of additional features.

A more mature example: https://github.com/stefanprodan/podinfo, k8s specific.

Try this podinfo implementation.

I have chosen the well known podinfo application as an example, and I have developed the base and some components associated to it.

Check out https://github.com/stefanprodan/podinfo it’s my go to for creating new microservices

It focuses on an "uninteresting" workload and uses podinfo as the sample app. This is because it's easy to deploy and customize with a sample Helm chart.