diff options
| author | Brendan Burns <bburns@google.com> | 2015-06-05 14:50:11 -0700 |
|---|---|---|
| committer | Brendan Burns <bburns@google.com> | 2015-06-09 13:35:52 -0700 |
| commit | 2f18beac68176d99d4137a59faee0e653571ff63 (patch) | |
| tree | 3666b0d2e24d092722a8df0907e1e1b26480f5f1 | |
| parent | 28951be8bb0fcaa9af59f0cad444c56ae7ecda21 (diff) | |
Purge cluster/kubectl.sh from nearly all docs.
Mark cluster/kubectl.sh as deprecated.
| -rw-r--r-- | flaky-tests.md | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/flaky-tests.md b/flaky-tests.md index 5eb09ec9..da5549c8 100644 --- a/flaky-tests.md +++ b/flaky-tests.md @@ -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. -```./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. 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: ```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. |