An Easy Command to Manually Test Something From Within a Kubernetes Cluster

When working with kubernetes, it is sometimes useful to spin up a container within a cluster to just test something quickly.

Sure, you can just exec onto a pod, but sometimes you need to work with jobs or cronjobs, which are not so easy to just exec onto.

One way to do this is to create a pod temporarily with the tools you need (such as busybox) just to test something, such as connectivity to a server (because of a recent firewall change) or to test inter-pod communication.

This command creates a debug-pod which will create an interactive prompt, and allow all egress traffic from the pod. It will also tear down the pod, when you exit, removing the network policy as well.

Let's see this in action:

Related posts:

We always say that the eyes are the windows to the soul, now you can express love with your eyes and let your eyes be filled with nothing but love. Everywhere you look, you will be filled with…

With the government putting a stop to households mixing (including casual relationships) to halt the spread of coronavirus, it means we’re more likely to head outdoors to socialise safely. When we’re…

If you work freelance, you work for yourself and do projects with different companies rather than being a company employee.Freelance, freelancer, and freelance worker, are terms commonly used for a…