|
7 | 7 |
|
8 | 8 | .Procedure
|
9 | 9 |
|
10 |
| -. Set the `KUBECONFIG` variable to the location of the administrator `kubeconfig`: |
11 |
| -+ |
12 |
| ----- |
13 |
| -$ export KUBECONFIG=${KUBECONFIG-$HOME/.kube/config} |
14 |
| ----- |
15 |
| - |
16 | 10 | . Execute Cluster Loader using the built-in test configuration, which deploys five
|
17 | 11 | template builds and waits for them to complete:
|
18 | 12 | +
|
19 | 13 | ----
|
20 |
| -$ cd /usr/libexec/atomic-openshift/ |
21 |
| -$ ./extended.test --ginkgo.focus="Load cluster" |
| 14 | +$ sudo podman run -v ${LOCAL_KUBECONFIG}:/root/.kube/config -i |
| 15 | +quay.io/openshift/origin-tests:v4.0 /bin/bash -c 'export |
| 16 | +KUBECONFIG=/root/.kube/config && openshift-tests run-test |
| 17 | +"[Feature:Performance][Serial][Slow] Load cluster should load the cluster |
| 18 | +[Suite:openshift]"' |
22 | 19 | ----
|
23 | 20 | +
|
24 | 21 | Alternatively, execute Cluster Loader with a user-defined configuration by
|
25 |
| -adding the flag for `--viper-config`: |
| 22 | +setting the environment variable for `VIPERCONFIG`: |
26 | 23 | +
|
27 | 24 | ----
|
28 |
| -$ ./extended.test --ginkgo.focus="Load cluster" --viper-config=config/test <1> |
| 25 | +$ sudo podman run -v ${LOCAL_KUBECONFIG}:/root/.kube/config -i |
| 26 | +quay.io/openshift/origin-tests:v4.0 /bin/bash -c 'export |
| 27 | +KUBECONFIG=/root/.kube/config && export VIPERCONFIG=config/test && |
| 28 | +openshift-tests run-test "[Feature:Performance][Serial][Slow] Load cluster |
| 29 | +should load the cluster [Suite:openshift]"' |
29 | 30 | ----
|
30 |
| -<1> In this example, there is a subdirectory called *_config/_* with a configuration |
| 31 | ++ |
| 32 | +In this example, there is a subdirectory called *_config/_* with a configuration |
31 | 33 | file called *_test.yml_*. In the command line, exclude the extension of the
|
32 | 34 | configuration file, as the tool will automatically determine the file type and
|
33 | 35 | extension.
|
0 commit comments