kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Purge cluster/kubectl.sh from nearly all docs. 

Mark cluster/kubectl.sh as deprecated.
This commit is contained in:
Brendan Burns 2015-06-05 14:50:11 -07:00
parent 28951be8bb
commit 2f18beac68
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
flaky-tests.md
View File

@ -33,7 +33,9 @@ spec:
``` ```
Note that we omit the labels and the selector fields of the replication controller, because they will be populated from the labels field of the pod template by default. Note that we omit the labels and the selector fields of the replication controller, because they will be populated from the labels field of the pod template by default.
```./cluster/kubectl.sh create -f controller.yaml``` ```
kubectl create -f controller.yaml
```
This will spin up 24 instances of the test. They will run to completion, then exit, and the kubelet will restart them, accumulating more and more runs of the test. This will spin up 24 instances of the test. They will run to completion, then exit, and the kubelet will restart them, accumulating more and more runs of the test.
You can examine the recent runs of the test by calling ```docker ps -a``` and looking for tasks that exited with non-zero exit codes. Unfortunately, docker ps -a only keeps around the exit status of the last 15-20 containers with the same image, so you have to check them frequently. You can examine the recent runs of the test by calling ```docker ps -a``` and looking for tasks that exited with non-zero exit codes. Unfortunately, docker ps -a only keeps around the exit status of the last 15-20 containers with the same image, so you have to check them frequently.
@ -52,7 +54,7 @@ grep "Exited ([^0])" output.txt
Eventually you will have sufficient runs for your purposes. At that point you can stop and delete the replication controller by running: Eventually you will have sufficient runs for your purposes. At that point you can stop and delete the replication controller by running:
```sh ```sh
./cluster/kubectl.sh stop replicationcontroller flakecontroller kubectl stop replicationcontroller flakecontroller
``` ```
If you do a final check for flakes with ```docker ps -a```, ignore tasks that exited -1, since that's what happens when you stop the replication controller. If you do a final check for flakes with ```docker ps -a```, ignore tasks that exited -1, since that's what happens when you stop the replication controller.