github/kubernetes
4
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

remove hack/e2e.go

Browse Source
This commit is contained in:
Benjamin Elder
2019-09-07 13:19:38 -07:00
committed by Davanum Srinivas
parent 2b3540068b
commit 83c56a0373
11 changed files with 11 additions and 629 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
cluster/addons/dns/nodelocaldns/README.md
View File

@@ -11,8 +11,6 @@ This feature is graduating to Beta in release 1.15.
This directory contains the addon config yaml - `nodelocaldns.yaml`
The variables will be substituted by the configure scripts when the yaml is copied into master.
To create a GCE cluster with nodelocaldns enabled, use the command:
`KUBE_ENABLE_NODELOCAL_DNS=true go run hack/e2e.go -v --up`
We have the following variables in the yaml:
`__PILLAR__DNS__SERVER__` - set to kube-dns service IP.

8
cluster/gce/util.sh
View File

@@ -3857,7 +3857,7 @@ function check-resources() {
}
# -----------------------------------------------------------------------------
# Cluster specific test helpers used from hack/e2e.go
# Cluster specific test helpers
# Execute prior to running tests to build a release if required for env.
#
@@ -3868,8 +3868,7 @@ function test-build-release() {
"${KUBE_ROOT}/build/release.sh"
}
# Execute prior to running tests to initialize required structure. This is
# called from hack/e2e.go only when running -up.
# Execute prior to running tests to initialize required structure.
#
# Assumed vars:
# Variables from config.sh
@@ -3925,8 +3924,7 @@ function test-setup() {
done
}
# Execute after running tests to perform any required clean-up. This is called
# from hack/e2e.go
# Execute after running tests to perform any required clean-up.
function test-teardown() {
detect-project
echo "Shutting down test cluster in background."

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

@@ -78,9 +78,9 @@ export KUBERNETES_NODE_PLATFORM=windows
export LOGGING_STACKDRIVER_RESOURCE_TYPES=new
```
Now bring up a cluster using one of the following two methods:
Now bring up a cluster using kube-up script:
#### 2a. Create a regular Kubernetes cluster
#### 2. Create a regular Kubernetes cluster
```
# Invoke kube-up.sh with these environment variables:
@@ -95,30 +95,6 @@ To teardown the cluster run:
PROJECT=${CLOUDSDK_CORE_PROJECT} KUBERNETES_SKIP_CONFIRM=y ./cluster/kube-down.sh
```
#### 2b. Create a Kubernetes end-to-end (E2E) test cluster
If you have built your own release binaries following step 1, run the following
command:
```
PROJECT=${CLOUDSDK_CORE_PROJECT} go run ./hack/e2e.go -- --up
```
Otherwise, you can specify what branch from which to get the release artifacts:
```
# Get the latest build from the stable1 branch
PROJECT=${CLOUDSDK_CORE_PROJECT} go run ./hack/e2e.go -- --up --extract=ci/k8s-stable1
# Or Get the latest build from master
PROJECT=${CLOUDSDK_CORE_PROJECT} go run ./hack/e2e.go -- --up --extract=ci-cross/latest
```
This command, by default, tears down any existing E2E cluster and creates a new
one. To teardown the cluster run the same command with `--down` instead of
`--up`.
No matter what type of cluster you chose to create, the result should be a
Kubernetes cluster with one Linux master node, `NUM_NODES` Linux worker nodes
and `NUM_WINDOWS_NODES` Windows worker nodes.
## Validating the cluster
Invoke this script to run a smoke test that verifies that the cluster has been