From cf29a21c9d921b50a0ac650de66dfd4925fd0fc2 Mon Sep 17 00:00:00 2001 From: Atsushi Torikoshi Date: Tue, 15 Nov 2022 23:33:50 +0900 Subject: [PATCH] Update the explanation for `kubectl describe pod`. Commit b60aa414a0b updated the command output samples, but explanations for the output of `kubectl describe pod` seems not to be updated. --- .../en/docs/tasks/debug/debug-application/debug-running-pod.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/tasks/debug/debug-application/debug-running-pod.md b/content/en/docs/tasks/debug/debug-application/debug-running-pod.md index f829b7821b..41af33da52 100644 --- a/content/en/docs/tasks/debug/debug-application/debug-running-pod.md +++ b/content/en/docs/tasks/debug/debug-application/debug-running-pod.md @@ -127,7 +127,7 @@ Restart Count tells you how many times the container has been restarted; this in Currently the only Condition associated with a Pod is the binary Ready condition, which indicates that the pod is able to service requests and should be added to the load balancing pools of all matching services. -Lastly, you see a log of recent events related to your Pod. The system compresses multiple identical events by indicating the first and last time it was seen and the number of times it was seen. "From" indicates the component that is logging the event, "SubobjectPath" tells you which object (e.g. container within the pod) is being referred to, and "Reason" and "Message" tell you what happened. +Lastly, you see a log of recent events related to your Pod. "From" indicates the component that is logging the event. "Reason" and "Message" tell you what happened. ## Example: debugging Pending Pods