Use make as the main build tool

This allows us to start building real dependencies into Makefile.

Leave old hack/* scripts in place but advise to use 'make'.  There are a few
rules that call things like 'go run' or 'build/*' that I left as-is for now.

1 files changed, 12 insertions, 12 deletions

diff --git a/e2e-node-tests.md b/e2e-node-tests.md
index 03ee4811..f4713855 100644
--- a/e2e-node-tests.md
+++ b/e2e-node-tests.md
@@ -57,7 +57,7 @@ Prerequisites:
 From the Kubernetes base directory, run:
 
 ```sh
-make test_e2e_node
+make test-e2e-node
 ```
 
 This will: run the *ginkgo* binary against the subdirectory *test/e2e_node*, which will in turn:
@@ -87,7 +87,7 @@ Prerequisites:
 Run:
 
 ```sh
-make test_e2e_node REMOTE=true
+make test-e2e-node REMOTE=true
 ```
 
 This will:
@@ -124,7 +124,7 @@ provided by the default image.
 List the available test images using gcloud.
 
 ```sh
-make test_e2e_node LIST_IMAGES=true
+make test-e2e-node LIST_IMAGES=true
 ```
 
 This will output a list of the available images for the default image project.
@@ -132,7 +132,7 @@ This will output a list of the available images for the default image project.
 Then run:
 
 ```sh
-make test_e2e_node REMOTE=true IMAGES="<comma-separated-list-images>"
+make test-e2e-node REMOTE=true IMAGES="<comma-separated-list-images>"
 ```
 
 ## Run tests against a running GCE instance (not an image)
@@ -140,7 +140,7 @@ make test_e2e_node REMOTE=true IMAGES="<comma-separated-list-images>"
 This is useful if you have an host instance running already and want to run the tests there instead of on a new instance.
 
 ```sh
-make test_e2e_node REMOTE=true HOSTS="<comma-separated-list-of-hostnames>"
+make test-e2e-node REMOTE=true HOSTS="<comma-separated-list-of-hostnames>"
 ```
 
 ## Delete instance after tests run
@@ -148,7 +148,7 @@ make test_e2e_node REMOTE=true HOSTS="<comma-separated-list-of-hostnames>"
 This is useful if you want recreate the instance for each test run to trigger flakes related to starting the instance.
 
 ```sh
-make test_e2e_node REMOTE=true DELETE_INSTANCES=true
+make test-e2e-node REMOTE=true DELETE_INSTANCES=true
 ```
 
 ## Keep instance, test binaries, and *processes* around after tests run
@@ -156,7 +156,7 @@ make test_e2e_node REMOTE=true DELETE_INSTANCES=true
 This is useful if you want to manually inspect or debug the kubelet process run as part of the tests.
 
 ```sh
-make test_e2e_node REMOTE=true CLEANUP=false
+make test-e2e-node REMOTE=true CLEANUP=false
 ```
 
 ## Run tests using an image in another project
@@ -164,7 +164,7 @@ make test_e2e_node REMOTE=true CLEANUP=false
 This is useful if you want to create your own host image in another project and use it for testing.
 
 ```sh
-make test_e2e_node REMOTE=true IMAGE_PROJECT="<name-of-project-with-images>" IMAGES="<image-name>"
+make test-e2e-node REMOTE=true IMAGE_PROJECT="<name-of-project-with-images>" IMAGES="<image-name>"
 ```
 
 Setting up your own host image may require additional steps such as installing etcd or docker.  See
@@ -176,7 +176,7 @@ This is useful if you want to create instances using a different name so that yo
 test in parallel against different instances of the same image.
 
 ```sh
-make test_e2e_node REMOTE=true INSTANCE_PREFIX="my-prefix"
+make test-e2e-node REMOTE=true INSTANCE_PREFIX="my-prefix"
 ```
 
 # Additional Test Options for both Remote and Local execution
@@ -186,13 +186,13 @@ make test_e2e_node REMOTE=true INSTANCE_PREFIX="my-prefix"
 To run tests matching a regex:
 
 ```sh
-make test_e2e_node REMOTE=true FOCUS="<regex-to-match>"
+make test-e2e-node REMOTE=true FOCUS="<regex-to-match>"
 ```
 
 To run tests NOT matching a regex:
 
 ```sh
-make test_e2e_node REMOTE=true SKIP="<regex-to-match>"
+make test-e2e-node REMOTE=true SKIP="<regex-to-match>"
 ```
 
 ## Run tests continually until they fail
@@ -202,7 +202,7 @@ run the tests until they fail.  **Note: this will only perform test setup once (
 less useful for catching flakes related creating the instance from an image.**
 
 ```sh
-make test_e2e_node REMOTE=true RUN_UNTIL_FAILURE=true
+make test-e2e-node REMOTE=true RUN_UNTIL_FAILURE=true
 ```
 
 # Notes on tests run by the Kubernetes project during pre-, post- submit.