From e13b255f898518c5dff657fb2c35d38e447a92d0 Mon Sep 17 00:00:00 2001 From: chenhuan12 Date: Wed, 22 Mar 2017 09:57:12 +0800 Subject: [PATCH] fix typo MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 1、Delete the row "NAME READY REASON RESTARTS AGE"; 2、fix command kubectl get nodes output. --- docs/user-guide/introspection-and-debugging.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/user-guide/introspection-and-debugging.md b/docs/user-guide/introspection-and-debugging.md index 47d1293900..ff0bb99539 100644 --- a/docs/user-guide/introspection-and-debugging.md +++ b/docs/user-guide/introspection-and-debugging.md @@ -120,7 +120,6 @@ A common scenario that you can detect using events is when you've created a Pod ```shell $ kubectl get pods -NAME READY REASON RESTARTS AGE NAME READY STATUS RESTARTS AGE nginx-deployment-1006230814-6winp 1/1 Running 0 7m nginx-deployment-1006230814-fmgu3 1/1 Running 0 7m @@ -264,11 +263,11 @@ Sometimes when debugging it can be useful to look at the status of a node -- for ```shell $ kubectl get nodes -NAME LABELS STATUS -kubernetes-node-861h kubernetes.io/hostname=kubernetes-node-861h NotReady -kubernetes-node-bols kubernetes.io/hostname=kubernetes-node-bols Ready -kubernetes-node-st6x kubernetes.io/hostname=kubernetes-node-st6x Ready -kubernetes-node-unaj kubernetes.io/hostname=kubernetes-node-unaj Ready +NAME STATUS AGE +kubernetes-node-861h NotReady 1h +kubernetes-node-bols Ready 1h +kubernetes-node-st6x Ready 1h +kubernetes-node-unaj Ready 1h $ kubectl describe node kubernetes-node-861h Name: kubernetes-node-861h