github/kubernetes
1
0
Fork 0
mirror of https://github.com/k3s-io/kubernetes.git synced 2025-07-29 06:27:05 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #3373 from a-robinson/flake

Browse Source 
Update the doc on how to test for flakiness to actually work and to use kubectl.
This commit is contained in:
Alex Robinson 2015-01-09 15:57:40 -08:00
commit 206b90604c
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/devel/flaky-tests.md
View File

@ -12,6 +12,8 @@ There is a testing image ```brendanburns/flake``` up on the docker hub. We will
Create a replication controller with the following config:
```yaml
id: flakeController
kind: ReplicationController
apiVersion: v1beta1
desiredState:
replicas: 24
replicaSelector:
@ -37,14 +39,14 @@ labels:
name: flake
```
```./cluster/kubecfg.sh -c controller.yaml create replicaControllers```
```./cluster/kubectl.sh create -f controller.yaml```
This will spin up 100 instances of the test. They will run to completion, then exit, the kubelet will restart them, eventually you will have sufficient
runs for your purposes, and you can stop the replication controller:
runs for your purposes, and you can stop the replication controller by setting the ```replicas``` field to 0 and then running:
```sh
./cluster/kubecfg.sh stop flakeController
./cluster/kubecfg.sh rm flakeController
./cluster/kubectl.sh update -f controller.yaml
./cluster/kubectl.sh delete -f controller.yaml
```
Now examine the machines with ```docker ps -a``` and look for tasks that exited with non-zero exit codes (ignore those that exited -1, since that's what happens when you stop the replica controller)