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: cluster/gce/windows/README-GCE-Windows-kube-up.md
+20-5Lines changed: 20 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,9 +56,8 @@ make quick-release
56
56
57
57
### 2. Create a Kubernetes cluster
58
58
59
-
You can create a regular Kubernetes cluster or an end-to-end test cluster.
60
-
End-to-end test clusters support running the Kubernetes e2e tests and enable
61
-
some debugging features such as SSH access on the Windows nodes.
59
+
You can create a regular Kubernetes cluster or an end-to-end test cluster.<br />
60
+
Only end-to-end test clusters support running the Kubernetes e2e tests (as both [e2e cluster creation](https://github.com/kubernetes/kubernetes/blob/b632eaddbaad9dc1430d214d506b72750bbb9f69/hack/e2e-internal/e2e-up.sh#L24) and [e2e test scripts](https://github.com/kubernetes/kubernetes/blob/b632eaddbaad9dc1430d214d506b72750bbb9f69/hack/ginkgo-e2e.sh#L42) are setup based on `cluster/gce/config-test.sh`), also enables some debugging features such as SSH access on the Windows nodes.
62
61
63
62
Please make sure you set the environment variables properly following the
If any e2e cluster exists already, this command will prompt you whether tears down and creates a new one. To teardown existing e2e cluster only, run the command:
0 commit comments