|
| 1 | +## To reproduce the test results, follow the steps to create a new Kubernetes cluster from scratch using Taikun: |
| 2 | +* Create a new project |
| 3 | +* Add 1 control plane node, 2 worker and 1 bastion |
| 4 | +* Commit the project |
| 5 | +* Wait for the cluster to be created |
| 6 | +* Create a kubeconfig with cluster-admin rights and download it |
| 7 | +* With the kubeconfig file you can run sonobouy as normal. |
| 8 | + * Replace ~/.kube/config, export KUBECONFIG=/wherever/kubeconfig.yaml, or use --kubeconfig. |
| 9 | + * You will need use a system able to connect to the cluster endpoint. |
| 10 | + |
| 11 | +## Running Conformance Tests |
| 12 | +The standard tool for running these tests is |
| 13 | +[Sonobuoy](https://github.com/vmware-tanzu/sonobuoy). Sonobuoy is regularly built and |
| 14 | +kept up to date to execute against all currently supported versions of |
| 15 | +kubernetes. |
| 16 | + |
| 17 | +Download a [binary release](https://github.com/vmware-tanzu/sonobuoy/releases) of the CLI, or build it yourself by running: |
| 18 | + |
| 19 | +``` |
| 20 | +$ go get -u -v github.com/vmware-tanzu/sonobuoy |
| 21 | +``` |
| 22 | + |
| 23 | +Deploy a Sonobuoy pod to your cluster with: |
| 24 | + |
| 25 | +``` |
| 26 | +$ sonobuoy run --mode=certified-conformance --wait --plugin-env e2e.E2E_EXTRA_ARGS="--non-blocking-taints=node-role.kubernetes.io/master,node-role.kubernetes.io/control-plane" |
| 27 | +``` |
| 28 | + |
| 29 | +View actively running pods: |
| 30 | + |
| 31 | +``` |
| 32 | +$ sonobuoy status |
| 33 | +``` |
| 34 | + |
| 35 | +To inspect the logs: |
| 36 | + |
| 37 | +``` |
| 38 | +$ sonobuoy logs |
| 39 | +``` |
| 40 | + |
| 41 | +Once `sonobuoy status` shows the run as `completed`, copy the output directory from the main Sonobuoy pod to |
| 42 | +a local directory: |
| 43 | + |
| 44 | +``` |
| 45 | +$ sonobuoy retrieve . |
| 46 | +``` |
| 47 | + |
| 48 | +This copies a single `.tar.gz` snapshot from the Sonobuoy pod into your local |
| 49 | +`.` directory. Extract the contents into `./results` with: |
| 50 | + |
| 51 | +``` |
| 52 | +mkdir ./results; tar xzf *.tar.gz -C ./results |
| 53 | +``` |
| 54 | + |
| 55 | +**NOTE:** The two files required for submission are located in the tarball under **plugins/e2e/results/{e2e.log,junit.xml}**. |
| 56 | + |
| 57 | +To clean up Kubernetes objects created by Sonobuoy, run: |
| 58 | + |
| 59 | +``` |
| 60 | +sonobuoy delete |
| 61 | +``` |
0 commit comments