Source: Dev.to | Jan 20, 2026 (UTC)
At various points in an Amazon EKS cluster’s lifecycle, direct access to a worker node may be required. This can be done using kubectl debug to open an interactive shell on the target node.
# start debug container kubectl debug nodes/<nodename> --profile=sysadmin -it --image=<image>
Enter fullscreen mode
Exit fullscreen mode
/host.chroot /host may fail.--profile=sysadmin flag.The sysadmin profile typically sets up the pod with:
/host 
Next to “switch” from the container filesystem you need to chroot /host And from there you are effectively in the node’s userland, and you can use the node’s binaries:
kubectl debug creates a debug pod with a name derived from the node name, so remember to delete the pod once you’re done debugging.
For further actions, you may consider blocking this person and/or reporting abuse
Залишити відповідь