diff --git a/README.md b/README.md
index b1af07dfb..9a5636195 100644
--- a/README.md
+++ b/README.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/README.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -116,6 +87,13 @@ Guide](../admin/README.md).
and how the version information gets embedded into the built binaries.
+
+
+
+
+
+
+
[]()
diff --git a/adding-an-APIGroup.md b/adding-an-APIGroup.md
index e0f95fc77..17fe534a9 100644
--- a/adding-an-APIGroup.md
+++ b/adding-an-APIGroup.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/adding-an-APIGroup.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -123,6 +94,13 @@ TODO: Add a troubleshooting section.
+
+
+
+
+
+
+
[]()
diff --git a/api-conventions.md b/api-conventions.md
index 757de2dd6..97ee0d86a 100644
--- a/api-conventions.md
+++ b/api-conventions.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/api-conventions.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
API Conventions
@@ -1377,6 +1348,13 @@ be less than 256", "must be greater than or equal to 0". Do not use words
like "larger than", "bigger than", "more than", "higher than", etc.
* When specifying numeric ranges, use inclusive ranges when possible.
+
+
+
+
+
+
+
[]()
diff --git a/api_changes.md b/api_changes.md
index 4ec383e73..a561d356c 100644
--- a/api_changes.md
+++ b/api_changes.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/api_changes.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -758,6 +729,13 @@ A releated issue is how a cluster manager can roll back from a new version
with a new feature, that is already being used by users. See
https://github.com/kubernetes/kubernetes/issues/4855.
+
+
+
+
+
+
+
[]()
diff --git a/automation.md b/automation.md
index 6ba74fd0d..b0cb4438a 100644
--- a/automation.md
+++ b/automation.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/automation.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -131,6 +102,13 @@ the issue number you found or filed.
Any pushes of new code to the PR will automatically trigger a new test. No human
interraction is required.
+
+
+
+
+
+
+
[]()
diff --git a/cherry-picks.md b/cherry-picks.md
index d5456a1a6..7fd8be13c 100644
--- a/cherry-picks.md
+++ b/cherry-picks.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/cherry-picks.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -106,11 +77,18 @@ requested - this should not be the norm, but it may happen.
See the [cherrypick queue dashboard](http://cherrypick.k8s.io/#/queue) for
status of PRs labeled as `cherrypick-candidate`.
-[Contributor License Agreements](http://releases.k8s.io/HEAD/CONTRIBUTING.md) is
+[Contributor License Agreements](http://releases.k8s.io/v1.4.0-alpha.0/CONTRIBUTING.md) is
considered implicit for all code within cherry-pick pull requests, ***unless
there is a large conflict***.
+
+
+
+
+
+
+
[]()
diff --git a/cli-roadmap.md b/cli-roadmap.md
index 7a7791b80..8d000ad46 100644
--- a/cli-roadmap.md
+++ b/cli-roadmap.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/cli-roadmap.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -40,6 +11,13 @@ See github issues with the following labels:
* [component/clientlib](https://github.com/kubernetes/kubernetes/labels/component/clientlib)
+
+
+
+
+
+
+
[]()
diff --git a/client-libraries.md b/client-libraries.md
index 95a3dfeb1..c36b1ad16 100644
--- a/client-libraries.md
+++ b/client-libraries.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/client-libraries.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -36,7 +7,7 @@ Documentation for other releases can be found at
### Supported
- * [Go](http://releases.k8s.io/HEAD/pkg/client/)
+ * [Go](http://releases.k8s.io/v1.4.0-alpha.0/pkg/client/)
### User Contributed
@@ -55,6 +26,13 @@ the core Kubernetes team*
* [Ruby](https://github.com/abonas/kubeclient)
* [Scala](https://github.com/doriordan/skuber)
+
+
+
+
+
+
+
[]()
diff --git a/coding-conventions.md b/coding-conventions.md
index 3a59cd2a7..1d7d75ac5 100644
--- a/coding-conventions.md
+++ b/coding-conventions.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/coding-conventions.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -176,6 +147,13 @@ using the system](../user-guide/config-best-practices.md)
- [Go landmines](https://gist.github.com/lavalamp/4bd23295a9f32706a48f)
+
+
+
+
+
+
+
[]()
diff --git a/collab.md b/collab.md
index 0742b5489..68c13df5b 100644
--- a/collab.md
+++ b/collab.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/collab.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -116,6 +87,13 @@ hold shall not be merged until the person who requested the hold acks the
review, withdraws their hold, or is overruled by a preponderance of maintainers.
+
+
+
+
+
+
+
[]()
diff --git a/developer-guides/vagrant.md b/developer-guides/vagrant.md
index 64bfa13f2..d87152efc 100644
--- a/developer-guides/vagrant.md
+++ b/developer-guides/vagrant.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/developer-guides/vagrant.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -447,6 +418,13 @@ provider, which uses nfs by default. For example:
export KUBERNETES_VAGRANT_USE_NFS=true
```
+
+
+
+
+
+
+
[]()
diff --git a/development.md b/development.md
index 9e0081913..550e4878f 100644
--- a/development.md
+++ b/development.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/development.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -48,7 +19,7 @@ branch, but release branches of Kubernetes should not change.
Official releases are built using Docker containers. To build Kubernetes using
Docker please follow [these
-instructions](http://releases.k8s.io/HEAD/build/README.md).
+instructions](http://releases.k8s.io/v1.4.0-alpha.0/build/README.md).
### Go development environment
@@ -320,6 +291,13 @@ hack/update-generated-docs.sh
```
+
+
+
+
+
+
+
[]()
diff --git a/e2e-node-tests.md b/e2e-node-tests.md
index f28691343..876ad526e 100644
--- a/e2e-node-tests.md
+++ b/e2e-node-tests.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/e2e-node-tests.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -217,6 +188,13 @@ The PR builder runs tests against the images listed in [jenkins-pull.properties]
The post submit tests run against the images listed in [jenkins-ci.properties](../../test/e2e_node/jenkins/jenkins-ci.properties)
+
+
+
+
+
+
+
[]()
diff --git a/e2e-tests.md b/e2e-tests.md
index b67d3a5ef..f1137a264 100644
--- a/e2e-tests.md
+++ b/e2e-tests.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/e2e-tests.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -664,6 +635,13 @@ You should also know the [testing conventions](coding-conventions.md#testing-con
+
+
+
+
+
+
+
[]()
diff --git a/faster_reviews.md b/faster_reviews.md
index eb7416d63..d6bc43bda 100644
--- a/faster_reviews.md
+++ b/faster_reviews.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/faster_reviews.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -235,6 +206,13 @@ a bit of thought into how your work can be made easier to review. If you do
these things your PRs will flow much more easily.
+
+
+
+
+
+
+
[]()
diff --git a/flaky-tests.md b/flaky-tests.md
index b599f80f4..e6563220a 100644
--- a/flaky-tests.md
+++ b/flaky-tests.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/flaky-tests.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -197,6 +168,13 @@ If you do a final check for flakes with `docker ps -a`, ignore tasks that exited
Happy flake hunting!
+
+
+
+
+
+
+
[]()
diff --git a/generating-clientset.md b/generating-clientset.md
index 42851cc93..ea4111034 100644
--- a/generating-clientset.md
+++ b/generating-clientset.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/generating-clientset.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -64,6 +35,13 @@ At the 1.2 release, we have two released clientsets in the repo: internalclients
+
+
+
+
+
+
+
[]()
diff --git a/getting-builds.md b/getting-builds.md
index ab1df171c..bc3223f9a 100644
--- a/getting-builds.md
+++ b/getting-builds.md
@@ -1,40 +1,11 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/getting-builds.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
# Getting Kubernetes Builds
-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).
+You can use [hack/get-build.sh](http://releases.k8s.io/v1.4.0-alpha.0/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.
@@ -74,6 +45,13 @@ $ curl -sSL https://storage.googleapis.com/pub/gsutil.tar.gz | sudo tar -xz -C /
$ sudo ln -s /usr/local/src/gsutil/gsutil /usr/bin/gsutil
```
+
+
+
+
+
+
+
[]()
diff --git a/how-to-doc.md b/how-to-doc.md
index 67bffe154..a978b9082 100644
--- a/how-to-doc.md
+++ b/how-to-doc.md
@@ -1,29 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -73,7 +49,7 @@ After running `hack/update-munge-docs.sh`, you'll see a table of contents genera
It's important to follow the rules when writing links. It helps us correctly versionize documents for each release.
-Use inline links instead of urls at all times. When you add internal links to `docs/` or `examples/`, use relative links; otherwise, use `http://releases.k8s.io/HEAD/`. For example, avoid using:
+Use inline links instead of urls at all times. When you add internal links to `docs/` or `examples/`, use relative links; otherwise, use `http://releases.k8s.io/v1.4.0-alpha.0/`. For example, avoid using:
```
[GCE](https://github.com/kubernetes/kubernetes/blob/master/docs/getting-started-guides/gce.md) # note that it's under docs/
@@ -85,11 +61,11 @@ Instead, use:
```
[GCE](../getting-started-guides/gce.md) # note that it's under docs/
-[Kubernetes package](http://releases.k8s.io/HEAD/pkg/) # note that it's under pkg/
+[Kubernetes package](http://releases.k8s.io/v1.4.0-alpha.0/pkg/) # note that it's under pkg/
[Kubernetes](http://kubernetes.io/) # external link
```
-The above example generates the following links: [GCE](../getting-started-guides/gce.md), [Kubernetes package](http://releases.k8s.io/HEAD/pkg/), and [Kubernetes](http://kubernetes.io/).
+The above example generates the following links: [GCE](../getting-started-guides/gce.md), [Kubernetes package](http://releases.k8s.io/v1.4.0-alpha.0/pkg/), and [Kubernetes](http://kubernetes.io/).
## How to Include an Example
@@ -170,7 +146,7 @@ Mungers are like gofmt for md docs which we use to format documents. To use it,
```
-in your md files. Note that xxxx is the placeholder for a specific munger. Appropriate content will be generated and inserted between two brackets after you run `hack/update-munge-docs.sh`. See [munger document](http://releases.k8s.io/HEAD/cmd/mungedocs/) for more details.
+in your md files. Note that xxxx is the placeholder for a specific munger. Appropriate content will be generated and inserted between two brackets after you run `hack/update-munge-docs.sh`. See [munger document](http://releases.k8s.io/v1.4.0-alpha.0/cmd/mungedocs/) for more details.
## Auto-added Mungers
@@ -183,8 +159,6 @@ UNVERSIONED_WARNING munger inserts unversioned warning which warns the users whe
```
-
-
```
diff --git a/instrumentation.md b/instrumentation.md
index 5e195f6b5..b8f153332 100644
--- a/instrumentation.md
+++ b/instrumentation.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/instrumentation.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
Instrumenting Kubernetes with a new metric
@@ -66,6 +37,13 @@ https://github.com/prometheus/client_golang/blob/master/prometheus/histogram.go
https://github.com/prometheus/client_golang/blob/master/prometheus/summary.go
+
+
+
+
+
+
+
[]()
diff --git a/issues.md b/issues.md
index 1a068faaf..e59025eab 100644
--- a/issues.md
+++ b/issues.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/issues.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -88,6 +59,13 @@ release if it gets done, but we wouldn't block the release on it. A few days
before release, we will probably move all P2 and P3 bugs out of that milestone
in bulk.
+
+
+
+
+
+
+
[]()
diff --git a/kubectl-conventions.md b/kubectl-conventions.md
index 23a73f111..258e25cbb 100644
--- a/kubectl-conventions.md
+++ b/kubectl-conventions.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/kubectl-conventions.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -407,6 +378,13 @@ method which configures the generated namespace that callers of the generator
creating it.
+
+
+
+
+
+
+
[]()
diff --git a/kubemark-guide.md b/kubemark-guide.md
index 3f93cd362..ed9ff7eef 100644
--- a/kubemark-guide.md
+++ b/kubemark-guide.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/kubemark-guide.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -239,6 +210,13 @@ it’s crucial to make it as simple as possible to allow running a big number of
Hollows on a single core.
+
+
+
+
+
+
+
[]()
diff --git a/logging.md b/logging.md
index f0350dcaa..bbeba7c03 100644
--- a/logging.md
+++ b/logging.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/logging.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -65,6 +36,13 @@ environments may wish to run at V(3) or V(4). If you wish to change the log
level, you can pass in `-v=X` where X is the desired maximum level to log.
+
+
+
+
+
+
+
[]()
diff --git a/making-release-notes.md b/making-release-notes.md
index 01ef369e7..889983125 100644
--- a/making-release-notes.md
+++ b/making-release-notes.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/making-release-notes.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -81,6 +52,13 @@ page.
* Press Save.
+
+
+
+
+
+
+
[]()
diff --git a/mesos-style.md b/mesos-style.md
index fdf9da08b..25055deae 100644
--- a/mesos-style.md
+++ b/mesos-style.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/mesos-style.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -247,6 +218,13 @@ Borg is described [here](http://research.google.com/pubs/pub43438.html).
+
+
+
+
+
+
+
[]()
diff --git a/node-performance-testing.md b/node-performance-testing.md
index 54c15dee0..4fec27642 100644
--- a/node-performance-testing.md
+++ b/node-performance-testing.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/node-performance-testing.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -156,6 +127,13 @@ More details on benchmarking [here](https://golang.org/pkg/testing/).
+
+
+
+
+
+
+
[]()
diff --git a/on-call-build-cop.md b/on-call-build-cop.md
index 7a91e5cb8..e0bfd240d 100644
--- a/on-call-build-cop.md
+++ b/on-call-build-cop.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/on-call-build-cop.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -181,6 +152,13 @@ the build cop is expected to file issues for any flaky tests they encounter.
[@k8s-oncall](https://github.com/k8s-oncall) will reach the current person on
call.
+
+
+
+
+
+
+
[]()
diff --git a/on-call-rotations.md b/on-call-rotations.md
index 6cf8d0bfa..a7ace0c0c 100644
--- a/on-call-rotations.md
+++ b/on-call-rotations.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/on-call-rotations.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -72,6 +43,13 @@ milestones, for instance).
* [Github and Build Cop Rotation](on-call-build-cop.md)
* [User Support Rotation](on-call-user-support.md)
+
+
+
+
+
+
+
[]()
diff --git a/on-call-user-support.md b/on-call-user-support.md
index 1e9f3cb39..f8d38866d 100644
--- a/on-call-user-support.md
+++ b/on-call-user-support.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/on-call-user-support.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -118,6 +89,13 @@ current person on call.
+
+
+
+
+
+
+
[]()
diff --git a/owners.md b/owners.md
index dcd144832..70acf71d5 100644
--- a/owners.md
+++ b/owners.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/owners.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -127,6 +98,13 @@ parent's OWNERS file is used instead. There will be a top-level OWNERS file to
Obviously changing the OWNERS file requires OWNERS permission.
+
+
+
+
+
+
+
[]()
diff --git a/profiling.md b/profiling.md
index 5e74d25fa..a95840f44 100644
--- a/profiling.md
+++ b/profiling.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/profiling.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -75,6 +46,13 @@ to get 30 sec. CPU profile.
To enable contention profiling you need to add line `rt.SetBlockProfileRate(1)` in addition to `m.mux.HandleFunc(...)` added before (`rt` stands for `runtime` in `master.go`). This enables 'debug/pprof/block' subpage, which can be used as an input to `go tool pprof`.
+
+
+
+
+
+
+
[]()
diff --git a/pull-requests.md b/pull-requests.md
index 6803c4646..4f3c60182 100644
--- a/pull-requests.md
+++ b/pull-requests.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/pull-requests.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -135,6 +106,13 @@ We use a variety of automation to manage pull requests. This automation is desc
[elsewhere.](automation.md)
+
+
+
+
+
+
+
[]()
diff --git a/releasing.md b/releasing.md
index 5747ed6b3..635a73872 100644
--- a/releasing.md
+++ b/releasing.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/releasing.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -302,6 +273,13 @@ can, for instance, tell it to override `gitVersion` and set it to
is the complete SHA1 of the (dirty) tree used at build time.
+
+
+
+
+
+
+
[]()
diff --git a/running-locally.md b/running-locally.md
index 6999e588f..f1f0f192a 100644
--- a/running-locally.md
+++ b/running-locally.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/running-locally.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
Getting started locally
@@ -192,6 +163,13 @@ KUBE_DNS_REPLICAS=1
To know more on DNS service you can look [here](http://issue.k8s.io/6667). Related documents can be found [here](../../build/kube-dns/#how-do-i-configure-it)
+
+
+
+
+
+
+
[]()
diff --git a/scheduler.md b/scheduler.md
index 778fd087b..d9b77e9a0 100755
--- a/scheduler.md
+++ b/scheduler.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/scheduler.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -54,30 +25,37 @@ divided by the node's capacity).
Finally, the node with the highest priority is chosen
(or, if there are multiple such nodes, then one of them is chosen at random). The code
for this main scheduling loop is in the function `Schedule()` in
-[plugin/pkg/scheduler/generic_scheduler.go](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/generic_scheduler.go)
+[plugin/pkg/scheduler/generic_scheduler.go](http://releases.k8s.io/v1.4.0-alpha.0/plugin/pkg/scheduler/generic_scheduler.go)
## Scheduler extensibility
The scheduler is extensible: the cluster administrator can choose which of the pre-defined
scheduling policies to apply, and can add new ones. The built-in predicates and priorities are
-defined in [plugin/pkg/scheduler/algorithm/predicates/predicates.go](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithm/predicates/predicates.go) and
-[plugin/pkg/scheduler/algorithm/priorities/priorities.go](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithm/priorities/priorities.go), respectively.
+defined in [plugin/pkg/scheduler/algorithm/predicates/predicates.go](http://releases.k8s.io/v1.4.0-alpha.0/plugin/pkg/scheduler/algorithm/predicates/predicates.go) and
+[plugin/pkg/scheduler/algorithm/priorities/priorities.go](http://releases.k8s.io/v1.4.0-alpha.0/plugin/pkg/scheduler/algorithm/priorities/priorities.go), respectively.
The policies that are applied when scheduling can be chosen in one of two ways. Normally,
the policies used are selected by the functions `defaultPredicates()` and `defaultPriorities()` in
-[plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go).
+[plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/v1.4.0-alpha.0/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go).
However, the choice of policies
can be overridden by passing the command-line flag `--policy-config-file` to the scheduler, pointing to a JSON
file specifying which scheduling policies to use. See
[examples/scheduler-policy-config.json](../../examples/scheduler-policy-config.json) for an example
config file. (Note that the config file format is versioned; the API is defined in
-[plugin/pkg/scheduler/api](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/api/)).
+[plugin/pkg/scheduler/api](http://releases.k8s.io/v1.4.0-alpha.0/plugin/pkg/scheduler/api/)).
Thus to add a new scheduling policy, you should modify predicates.go or priorities.go,
and either register the policy in `defaultPredicates()` or `defaultPriorities()`, or use a policy config file.
## Exploring the code
If you want to get a global picture of how the scheduler works, you can start in
-[plugin/cmd/kube-scheduler/app/server.go](http://releases.k8s.io/HEAD/plugin/cmd/kube-scheduler/app/server.go)
+[plugin/cmd/kube-scheduler/app/server.go](http://releases.k8s.io/v1.4.0-alpha.0/plugin/cmd/kube-scheduler/app/server.go)
+
+
+
+
+
+
+
diff --git a/scheduler_algorithm.md b/scheduler_algorithm.md
index 807f0600d..2cf0c54de 100755
--- a/scheduler_algorithm.md
+++ b/scheduler_algorithm.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/scheduler_algorithm.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -50,7 +21,7 @@ The purpose of filtering the nodes is to filter out the nodes that do not meet c
- `MaxGCEPDVolumeCount`: Ensure that the number of attached GCE PersistentDisk volumes does not exceed a maximum value (by default, 16, which is the maximum GCE allows -- see [GCE's documentation](https://cloud.google.com/compute/docs/disks/persistent-disks#limits_for_predefined_machine_types)). The maximum value can be controlled by setting the `KUBE_MAX_PD_VOLS` environment variable.
- `CheckNodeMemoryPressure`: Check if a pod can be scheduled on a node reporting memory pressure condition. Currently, no ``BestEffort`` should be placed on a node under memory pressure as it gets automatically evicted by kubelet.
-The details of the above predicates can be found in [plugin/pkg/scheduler/algorithm/predicates/predicates.go](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithm/predicates/predicates.go). All predicates mentioned above can be used in combination to perform a sophisticated filtering policy. Kubernetes uses some, but not all, of these predicates by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go).
+The details of the above predicates can be found in [plugin/pkg/scheduler/algorithm/predicates/predicates.go](http://releases.k8s.io/v1.4.0-alpha.0/plugin/pkg/scheduler/algorithm/predicates/predicates.go). All predicates mentioned above can be used in combination to perform a sophisticated filtering policy. Kubernetes uses some, but not all, of these predicates by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/v1.4.0-alpha.0/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go).
## Ranking the nodes
@@ -69,7 +40,14 @@ Currently, Kubernetes scheduler provides some practical priority functions, incl
- `ImageLocalityPriority`: Nodes are prioritized based on locality of images requested by a pod. Nodes with larger size of already-installed packages required by the pod will be preferred over nodes with no already-installed packages required by the pod or a small total size of already-installed packages required by the pod.
- `NodeAffinityPriority`: (Kubernetes v1.2) Implements `preferredDuringSchedulingIgnoredDuringExecution` node affinity; see [here](../user-guide/node-selection/) for more details.
-The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithm/priorities/). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/HEAD/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [scheduler.md](scheduler.md) for how to customize).
+The details of the above priority functions can be found in [plugin/pkg/scheduler/algorithm/priorities](http://releases.k8s.io/v1.4.0-alpha.0/plugin/pkg/scheduler/algorithm/priorities/). Kubernetes uses some, but not all, of these priority functions by default. You can see which ones are used by default in [plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go](http://releases.k8s.io/v1.4.0-alpha.0/plugin/pkg/scheduler/algorithmprovider/defaults/defaults.go). Similar as predicates, you can combine the above priority functions and assign weight factors (positive number) to them as you want (check [scheduler.md](scheduler.md) for how to customize).
+
+
+
+
+
+
+
diff --git a/testing.md b/testing.md
index 72f1c3282..faa1f66a9 100644
--- a/testing.md
+++ b/testing.md
@@ -1,29 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -195,6 +171,13 @@ hack/test-integration.sh # Run all integration tests.
Please refer to [End-to-End Testing in Kubernetes](e2e-tests.md).
+
+
+
+
+
+
+
[]()
diff --git a/update-release-docs.md b/update-release-docs.md
index 1dbb20a88..211659971 100644
--- a/update-release-docs.md
+++ b/update-release-docs.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/update-release-docs.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -144,6 +115,13 @@ docs go away.
If the change added or deleted a doc, then update the corresponding `_includes/nav_vX.Y.html` file as well.
+
+
+
+
+
+
+
[]()
diff --git a/updating-docs-for-feature-changes.md b/updating-docs-for-feature-changes.md
index f0f3197d9..6d7ec92b5 100644
--- a/updating-docs-for-feature-changes.md
+++ b/updating-docs-for-feature-changes.md
@@ -1,29 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -100,6 +76,13 @@ Anyone making user facing changes to kubernetes. This is especially important f
* *TODO once we have a standard widget set we are happy with* - include diagrams to help describe complex ideas (not required yet)
+
+
+
+
+
+
+
[]()
diff --git a/writing-a-getting-started-guide.md b/writing-a-getting-started-guide.md
index fbe5aa1ba..f4f86b54e 100644
--- a/writing-a-getting-started-guide.md
+++ b/writing-a-getting-started-guide.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/writing-a-getting-started-guide.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -130,6 +101,13 @@ These guidelines say *what* to do. See the Rationale section for *why*.
+
+
+
+
+
+
+
[]()
diff --git a/writing-good-e2e-tests.md b/writing-good-e2e-tests.md
index 2cb0fe47a..18c6877f2 100644
--- a/writing-good-e2e-tests.md
+++ b/writing-good-e2e-tests.md
@@ -1,34 +1,5 @@
-
-
-
-
-
-
-
-
-PLEASE NOTE: This document applies to the HEAD of the source tree
-
-If you are using a released version of Kubernetes, you should
-refer to the docs that go with that version.
-
-
-
-The latest release of this document can be found
-[here](http://releases.k8s.io/release-1.2/docs/devel/writing-good-e2e-tests.md).
-
-Documentation for other releases can be found at
-[releases.k8s.io](http://releases.k8s.io).
-
---
-
-
@@ -264,6 +235,13 @@ Note that opening issues for specific better tooling is welcome, and
code implementing that tooling is even more welcome :-).
+
+
+
+
+
+
+
[]()