Skip to content

Commit 8727eef

Browse files
authored
Merge pull request kubernetes#85836 from YangLu1031/master
Add instructions about how to bring up e2e test cluster
2 parents c72d5fd + b88788b commit 8727eef

File tree

1 file changed

+20
-5
lines changed

1 file changed

+20
-5
lines changed

cluster/gce/windows/README-GCE-Windows-kube-up.md

Lines changed: 20 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -56,9 +56,8 @@ make quick-release
5656

5757
### 2. Create a Kubernetes cluster
5858

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.
6261

6362
Please make sure you set the environment variables properly following the
6463
instructions in the previous section.
@@ -78,9 +77,9 @@ export KUBERNETES_NODE_PLATFORM=windows
7877
export LOGGING_STACKDRIVER_RESOURCE_TYPES=new
7978
```
8079

81-
Now bring up a cluster using kube-up script:
80+
Now bring up a cluster using one of the following two methods:
8281

83-
#### 2. Create a regular Kubernetes cluster
82+
#### 2a. Create a regular Kubernetes cluster
8483

8584
```
8685
# Invoke kube-up.sh with these environment variables:
@@ -95,6 +94,22 @@ To teardown the cluster run:
9594
PROJECT=${CLOUDSDK_CORE_PROJECT} KUBERNETES_SKIP_CONFIRM=y ./cluster/kube-down.sh
9695
```
9796

97+
#### 2b. Create a Kubernetes end-to-end (E2E) test cluster
98+
If you have built your own release binaries following step 1, run the following
99+
command:
100+
```
101+
PROJECT=${CLOUDSDK_CORE_PROJECT} ./hack/e2e-internal/e2e-up.sh
102+
```
103+
104+
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:
105+
```
106+
PROJECT=${CLOUDSDK_CORE_PROJECT} ./hack/e2e-internal/e2e-down.sh
107+
```
108+
109+
No matter what type of cluster you chose to create, the result should be a
110+
Kubernetes cluster with one Linux master node, `NUM_NODES` Linux worker nodes
111+
and `NUM_WINDOWS_NODES` Windows worker nodes.
112+
98113
## Validating the cluster
99114

100115
Invoke this script to run a smoke test that verifies that the cluster has been

0 commit comments

Comments
 (0)