Upgrades and upgrade tests take versions of the form release/stable instead of stable_release:

- Refactor common and gce/upgrade.sh to use arbitrary published releases
- Update hack/get-build to use cluster/common code
- Use hack/get-build.sh in cluster upgrade test logic

1 files changed, 17 insertions, 7 deletions

diff --git a/getting-builds.md b/getting-builds.md
index bcb981c4..3803c873 100644
--- a/getting-builds.md
+++ b/getting-builds.md
@@ -35,17 +35,27 @@ Documentation for other releases can be found at
 
 You can use [hack/get-build.sh](http://releases.k8s.io/HEAD/hack/get-build.sh) to or use as a reference on how to get the most recent builds with curl. With `get-build.sh` you can grab the most recent stable build, the most recent release candidate, or the most recent build to pass our ci and gce e2e tests (essentially a nightly build).
 
+Run `./hack/get-build.sh -h` for its usage.
+
+For example, to get a build at a specific version (v1.0.2):
+
 ```console
-usage:
-  ./hack/get-build.sh [stable|release|latest|latest-green]
+./hack/get-build.sh v1.0.2
+```
 
-        stable:        latest stable version
-        release:       latest release candidate
-        latest:        latest ci build
-        latest-green:  latest ci build to pass gce e2e
+Alternatively, to get the latest stable release:
+
+```console
+./hack/get-build.sh release/stable
+```
+
+Finally, you can just print the latest or stable version:
+
+```console
+./hack/get-build.sh -v ci/latest
 ```
 
-You can also use the gsutil tool to explore the Google Cloud Storage release bucket. Here are some examples:
+You can also use the gsutil tool to explore the Google Cloud Storage release buckets. Here are some examples:
 
 ```sh
 gsutil cat gs://kubernetes-release/ci/latest.txt          # output the latest ci version number