Can we interact and troubleshoot containers inside kubernetes without command line access?

2/6/2019

Can we interact and troubleshoot containers inside kubernetes without command line access? Or reading logs will be sufficient for debugging? Is there any way for debugging the containers without command line (kubectl)?

-- FNU
docker
docker-container
kubectl
kubernetes

2 Answers

2/6/2019

You can set up access to the dashboard and make changes to the containers / read logs there.

https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/

-- Ho Man
Source: StackOverflow

2/6/2019

Unfortunately the containers created FROM Scratch are not simple to debug, the best you can do is add logging and telemetry in the container so that you don't have to debug it. The other option is use minimal images like busybox.

The K8s team has a proposal for a a kubectl debug target-pod command, but is not something you can use yet.

In the worse scenarios you can try Scratch-debugger, it will create a busybox pod in the same node your pod being debuged is and call docker to inject the filesystem into the existing container.

-- Diego Mendes
Source: StackOverflow