whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix typo

Browse Source 
1、Delete the row "NAME             READY     REASON    RESTARTS   AGE";
2、fix command kubectl get nodes output.
This commit is contained in:
chenhuan12
2017-03-22 09:57:12 +08:00
committed by Andrew Chen
parent 3bf7d6658a
commit e13b255f89
1 changed files with 5 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/user-guide/introspection-and-debugging.md
+5 -6
View File
@@ -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