kubernetes

For security reasons, you might find your database (or any service for that matter) in an internal subnet, somewhere in the cloud. Accessing this for local debugging/development can be a pain. Using Kubernetes (assuming you have a cluster already), you can use this to your advantage. Create the tunnel What you need: Kubernetes (with API access via kubectl ofcourse) An image with netcat installed (Nice opportunity to punt mine 😉) tcpserver (should come with any Debian based distro) Next, ensure your pod is running....

Premise I often find myself needing to debug some network issue on Kubernetes. This is usually something like doing a traceroute to an external or internal address, checking egress IP addresses, or just needing a shell on the Kubernetes cluster. The Past What I used to do is find any running pod on the cluster and shell into it, hoping it’s running some sort of base Alpine/Debian image. Then I’d use whatever the built-in package manager is (apt, yum, etc) to install my the tools (nmap, traceroute, ping, etc)....