You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/src/developers/development.md
+19-11
Original file line number
Diff line number
Diff line change
@@ -416,23 +416,31 @@ To run the Kubernetes Conformance test suite locally, you can run
416
416
./scripts/ci-conformance.sh
417
417
```
418
418
419
-
With the following environment variables defined, you can build a CAPZ cluster from the HEAD of Kubernetes main branch or release branch, and run the Conformance test suite against it:
|`WINDOWS`|`false`| Run conformance against Windows nodes |
424
+
|`CONFORMANCE_NODES`|`1`|Number of parallel ginkgo nodes to run |
425
+
426
+
With the following environment variables defined, you can build a CAPZ cluster from the HEAD of Kubernetes main branch or release branch, and run the Conformance test suite against it. This is not enabled for Windows currently.
427
+
428
+
| Environment Variable | Value |
429
+
|----------------------|--------|
430
+
|`E2E_ARGS`|`-kubetest.use-ci-artifacts`|
424
431
|`KUBERNETES_VERSION`|`latest` - extract Kubernetes version from https://dl.k8s.io/ci/latest.txt (main's HEAD)<br>`latest-1.21` - extract Kubernetes version from https://dl.k8s.io/ci/latest-1.21.txt (release branch's HEAD) |
425
432
433
+
426
434
With the following environment variables defined, CAPZ runs `./scripts/ci-build-kubernetes.sh` as part of `./scripts/ci-conformance.sh`, which allows developers to build Kubernetes from source and run the Kubernetes Conformance test suite against a CAPZ cluster based on the custom build:
Copy file name to clipboardExpand all lines: test/e2e/e2e_suite_test.go
+4-1
Original file line number
Diff line number
Diff line change
@@ -92,6 +92,9 @@ var (
92
92
// kubetestConfigFilePath is the path to the kubetest configuration file
93
93
kubetestConfigFilePathstring
94
94
95
+
// kubetestRepoListPath
96
+
kubetestRepoListPathstring
97
+
95
98
// useCIArtifacts specifies whether or not to use the latest build from the main branch of the Kubernetes repository
96
99
useCIArtifactsbool
97
100
@@ -242,7 +245,7 @@ func init() {
242
245
flag.BoolVar(&skipCleanup, "e2e.skip-resource-cleanup", false, "if true, the resource cleanup after tests will be skipped")
243
246
flag.BoolVar(&useExistingCluster, "e2e.use-existing-cluster", false, "if true, the test uses the current cluster instead of creating a new one (default discovery rules apply)")
244
247
flag.StringVar(&kubetestConfigFilePath, "kubetest.config-file", "", "path to the kubetest configuration file")
245
-
248
+
flag.StringVar(&kubetestRepoListPath, "kubetest.repo-list-file", "", "path to the kubetest repo-list file")
0 commit comments