"Kubectl debug"의 두 판 사이의 차이

2023년 6월 1일 (목) 19:43 기준 최신판

1 개요[ | ]

kubectl debug

root@localhost:~# kubectl get no
NAME                               STATUS   ROLES    AGE   VERSION
cluster1-nodepool1-765bcd43-ef2h   Ready    <none>   12d   v1.20.15

root@localhost:~# kubectl debug node/cluster1-nodepool1-765bcd43-ef2h -it --image=busybox
Creating debugging pod node-debugger-cluster1-nodepool1-765bcd43-ef2h-z7vj2 with container debugger on node cluster1-node1-765bcd43-ef2h.
If you don't see a command prompt, try pressing enter.

/ # hostname
cluster1-nodepool1-765bcd43-ef2h

/ # ps -opid,comm | grep kube
 1734 kubelet
 2372 kube-proxy

/ # exit
root@localhost:~# kubectl get pod | grep node-debugger
node-debugger-cluster1-nodepool1-765bcd43-ef2h-z7vj2   0/1     Completed   0          90s

root@localhost:~# kubectl delete pod node-debugger-cluster1-nodepool1-765bcd43-ef2h-z7vj2
pod "node-debugger-cluster1-nodepool1-765bcd43-ef2h-z7vj2" deleted

2 같이 보기[ | ]

3 참고[ | ]

https://kubernetes.io/docs/tasks/debug-application-cluster/debug-running-pod/#node-shell-session

@@ 5번째 줄: / 5번째 줄: @@
 <syntaxhighlight lang='console'>
 root@localhost:~# kubectl get no
-NAME                           STATUS   ROLES    AGE   VERSION
+NAME                               STATUS   ROLES    AGE   VERSION
-cluster1-node1-765bcd43-ef2h   Ready    <none>   12d   v1.20.15
+cluster1-nodepool1-765bcd43-ef2h   Ready    <none>   12d   v1.20.15
-root@localhost:~# kubectl debug node/cluster1-node1-765bcd43-ef2h -it --image=busybox
+</syntaxhighlight>
-Creating debugging pod node-debugger-cluster1-node1-765bcd43-ef2h with container debugger on node cluster1-node1-765bcd43-ef2h.
+<syntaxhighlight lang='console'>
+root@localhost:~# kubectl debug node/cluster1-nodepool1-765bcd43-ef2h -it --image=busybox
+Creating debugging pod node-debugger-cluster1-nodepool1-765bcd43-ef2h-z7vj2 with container debugger on node cluster1-node1-765bcd43-ef2h.
 If you don't see a command prompt, try pressing enter.
+</syntaxhighlight>
+<syntaxhighlight lang='console'>
 / # hostname
-cluster1-node1-765bcd43-ef2h
+cluster1-nodepool1-765bcd43-ef2h
-/ # ps -ocomm | grep kube
+</syntaxhighlight>
-kubelet
+<syntaxhighlight lang='console'>
-kube-proxy
+/ # ps -opid,comm | grep kube
+kubelet
+kube-proxy
+</syntaxhighlight>
+<syntaxhighlight lang='console'>
+/ # exit
+root@localhost:~# kubectl get pod | grep node-debugger
+node-debugger-cluster1-nodepool1-765bcd43-ef2h-z7vj2   0/1     Completed   0          90s
+</syntaxhighlight>
+<syntaxhighlight lang='console'>
+root@localhost:~# kubectl delete pod node-debugger-cluster1-nodepool1-765bcd43-ef2h-z7vj2
+pod "node-debugger-cluster1-nodepool1-765bcd43-ef2h-z7vj2" deleted
 </syntaxhighlight>
 ==같이 보기==
+{{z컬럼3|
 * [[kubectl exec]]
+* [[kubectl get no]]
+* [[kubectl get pod]]
+* [[kubectl delete pod]]
+* [[error: ephemeral containers are disabled for this cluster]]
+}}
 ==참고==