kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Clarify privileges of kubectl debug node 

Signed-off-by: Kevin Grigorenko <kevin.grigorenko@us.ibm.com>
pull/35856/head
Kevin Grigorenko 2022-08-10 09:51:42 -05:00
parent 8140665391
commit 20ab45fb78
No known key found for this signature in database
GPG Key ID: 3B940C20C29BA13C
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
content/en/docs/tasks/debug/debug-application/debug-running-pod.md
View File

@ -611,8 +611,8 @@ kubectl delete pod myapp myapp-debug
## Debugging via a shell on the node {#node-shell-session}
If none of these approaches work, you can find the Node on which the Pod is
running and create a privileged Pod running in the host namespaces. To create
an interactive shell on a node using `kubectl debug`, run:
running and create a Pod running on the Node. To create
an interactive shell on a Node using `kubectl debug`, run:
```shell
kubectl debug node/mynode -it --image=ubuntu
@ -628,8 +628,11 @@ When creating a debugging session on a node, keep in mind that:
* `kubectl debug` automatically generates the name of the new Pod based on
the name of the Node.
* The container runs in the host IPC, Network, and PID namespaces.
* The root filesystem of the Node will be mounted at `/host`.
* The container runs in the host IPC, Network, and PID namespaces, although
the pod isn't privileged, so reading some process information may fail,
and `chroot /host` will fail.
* If you need a privileged pod, create it manually.
Don't forget to clean up the debugging Pod when you're finished with it: