github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-09-08 04:32:37 +00:00
Code Issues Projects Releases Wiki Activity

Purge cluster/kubectl.sh from nearly all docs.

Browse Source 
Mark cluster/kubectl.sh as deprecated.
This commit is contained in:
Brendan Burns
2015-06-05 14:50:11 -07:00
parent 6a979704b7
commit 9e198a6ed9
22 changed files with 149 additions and 140 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
examples/liveness/README.md
View File

@@ -36,13 +36,13 @@ This [guide](https://github.com/GoogleCloudPlatform/kubernetes/blob/master/examp
## Get your hands dirty
To show the health check is actually working, first create the pods:
```
# cluster/kubectl.sh create -f exec-liveness.yaml
# kubectl create -f exec-liveness.yaml
# cluster/kbuectl.sh create -f http-liveness.yaml
```
Check the status of the pods once they are created:
```
# cluster/kubectl.sh get pods
# kubectl get pods
POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS CREATED MESSAGE
liveness-exec 10.244.3.7 kubernetes-minion-f08h/130.211.122.180 test=liveness Running 3 seconds
liveness gcr.io/google_containers/busybox Running 2 seconds
@@ -52,7 +52,7 @@ liveness-http 10.244.0.8
Check the status half a minute later, you will see the termination messages:
```
# cluster/kubectl.sh get pods
# kubectl get pods
POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS CREATED MESSAGE
liveness-exec 10.244.3.7 kubernetes-minion-f08h/130.211.122.180 test=liveness Running 34 seconds
liveness gcr.io/google_containers/busybox Running 3 seconds last termination: exit code 137
@@ -63,7 +63,7 @@ The termination messages indicate that the liveness probes have failed, and the
You can also see the container restart count being incremented by running `kubectl describe`.
```
# cluster/kubectl.sh describe pods liveness-exec | grep "Restart Count"
# kubectl describe pods liveness-exec | grep "Restart Count"
Restart Count: 8
```