The NextGen gateway now includes a new debugging feature that allows you to troubleshoot Pods running on a Kubernetes Node, especially if they are experiencing crashes. To diagnose any connectivity problems from within the container, you can launch the Debug Container.
How to launch the Debug Container
Note
The “Connectivity Debugger” tool is available starting from Gateway version 16.0.0.Before you begin to launch the debug container:
- The NextGen gateway Pod should be scheduled and running.
- For the advanced debugging steps, you need to know which Node the Pod is running and must have shell access to run the commands on that Node.
Debugging with an ephemeral debug container
Ephemeral containers are useful for interactive troubleshooting when kubectl
exec is insufficient because a container has crashed or a container image does not include debugging utilities.
OpsRamp provides a new debugger docker image that includes all necessary debugging utilities.
Example 1: Debug using ephemeral containers
You can add ephemeral containers to a running NextGen gateway Pod using the kubectl
debug command. If you use the -i/--interactive
argument, the kubectl
command will automatically connect to the ephemeral container’s console.
Examples 2: Debug using debugging utilities