<p>Currently if I'm about to inspect my container, I have to do three steps:</p>
<ol>
<li>kubectl get all -n {NameSpace}</li>
<li>kubectl describe {Podname from step 1} -n {NameSpace}</li>
<li>Find the Node Host and the container ID (My eyes are complaning!)</li>
<li>Switch to the host and execute &quot;docker exec -ti -u root {Container ID} bash&quot;</li>
</ol>
<p>I am so mad about it right now. Wish somebody could offer some help to me and those who may share the same issue.</p>

Steve Wu
<blockquote>
<p>Pods are the smallest deployable units of computing that you can
create and manage in Kubernetes.</p>
</blockquote>
<p>So, if you want to &quot;enter&quot; a container, you just need to &quot;exec&quot; into the pod in a particular namespace. Kubernetes will get you the shell/command for that pod.</p>
<pre><code>kubectl -n somenamespace exec -it podname -- bash
</code></pre>
<p>There is no need to mention the node here as Kubernetes internally knows on which node the pod is scheduled.</p>
<blockquote>
<p>If a Pod has more than one container, use --container or -c to specify
a container in the kubectl exec command. For example, suppose you have
a Pod named my-pod, and the Pod has two containers named main-app and
helper-app. The following command would open a shell to the main-app
container.</p>
</blockquote>
<pre><code>kubectl exec -it my-pod -c main-app -- /bin/bash
</code></pre>
<p><a href="https://kubernetes.io/docs/tasks/debug-application-cluster/get-shell-running-container/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/debug-application-cluster/get-shell-running-container/</a></p>
