Skip to content

Commit b4f5238

Browse files
committed
Add instructions about how to use kubetest to bring up e2e test cluster
1 parent 641d029 commit b4f5238

File tree

1 file changed

+40
-2
lines changed

1 file changed

+40
-2
lines changed

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

Lines changed: 40 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -78,9 +78,9 @@ export KUBERNETES_NODE_PLATFORM=windows
7878
export LOGGING_STACKDRIVER_RESOURCE_TYPES=new
7979
```
8080

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

83-
#### 2. Create a regular Kubernetes cluster
83+
#### 2a. Create a regular Kubernetes cluster
8484

8585
```
8686
# Invoke kube-up.sh with these environment variables:
@@ -95,6 +95,44 @@ To teardown the cluster run:
9595
PROJECT=${CLOUDSDK_CORE_PROJECT} KUBERNETES_SKIP_CONFIRM=y ./cluster/kube-down.sh
9696
```
9797

98+
#### 2b. Create a Kubernetes end-to-end (E2E) test cluster
99+
100+
Install or update `kubetest` as follows:
101+
```
102+
go get -u k8s.io/test-infra/kubetest
103+
```
104+
* If you see the error below, it's due to `github.com/Azure/go-autorest` dependencies are incompatible between different versions of go modules:
105+
106+
```
107+
build k8s.io/test-infra/kubetest: cannot load github.com/Azure/go-autorest/autorest: ambiguous import: found github.com/Azure/go-autorest/autorest in multiple modules:
108+
github.com/Azure/go-autorest v11.1.2+incompatible (/usr/local/google/home/yluu/go/pkg/mod/github.com/!azure/[email protected]+incompatible/autorest)
109+
github.com/Azure/go-autorest/autorest v0.9.0 (/usr/local/google/home/yluu/go/pkg/mod/github.com/!azure/go-autorest/[email protected])
110+
```
111+
112+
Add `github.com/Azure/go-autorest v12.2.0+incompatible` into require block of `go.mod` and try again.
113+
114+
If you have built your own release binaries following step 1, run the following
115+
command:
116+
```
117+
PROJECT=${CLOUDSDK_CORE_PROJECT} $GOPATH/bin/kubetest --up
118+
```
119+
120+
Otherwise, you can specify what branch from which to get the release artifacts:
121+
```
122+
# Get the latest build from the stable1 branch
123+
PROJECT=${CLOUDSDK_CORE_PROJECT} $GOPATH/bin/kubetest --up --extract=ci/k8s-stable1
124+
# Or Get the latest build from master
125+
PROJECT=${CLOUDSDK_CORE_PROJECT} $GOPATH/bin/kubetest --up --extract=ci-cross/latest
126+
```
127+
128+
This command, by default, tears down any existing E2E cluster and creates a new
129+
one. To teardown the cluster run the same command with `--down` instead of
130+
`--up`.
131+
132+
No matter what type of cluster you chose to create, the result should be a
133+
Kubernetes cluster with one Linux master node, `NUM_NODES` Linux worker nodes
134+
and `NUM_WINDOWS_NODES` Windows worker nodes.
135+
98136
## Validating the cluster
99137
100138
Invoke this script to run a smoke test that verifies that the cluster has been

0 commit comments

Comments
 (0)