From 6ddca1d62f1edcd6c8faf9c2a4cf460f2eb60b77 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Wed, 4 Oct 2017 14:27:41 -0700 Subject: [PATCH] Update links to avoid redirects. (#5763) --- docs/concepts/cluster-administration/federation.md | 2 +- docs/concepts/overview/working-with-objects/labels.md | 2 +- docs/concepts/workloads/controllers/replicaset.md | 2 +- docs/getting-started-guides/binary_release.md | 2 +- docs/tasks/debug-application-cluster/debug-cluster.md | 2 +- docs/tutorials/stateful-application/zookeeper.md | 2 +- 6 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/concepts/cluster-administration/federation.md b/docs/concepts/cluster-administration/federation.md index fa04c6287e..70ae16791c 100644 --- a/docs/concepts/cluster-administration/federation.md +++ b/docs/concepts/cluster-administration/federation.md @@ -34,7 +34,7 @@ why you might want multiple clusters are: * Fault isolation: It might be better to have multiple small clusters rather than a single large cluster for fault isolation (for example: multiple clusters in different availability zones of a cloud provider). - See [Multi cluster guide](/docs/admin/multi-cluster) for details. + See [Multi cluster guide](/docs/concepts/cluster-administration/federation/) for details. * Scalability: There are scalability limits to a single kubernetes cluster (this should not be the case for most users. For more details: [Kubernetes Scaling and Performance Goals](https://git.k8s.io/community/sig-scalability/goals.md)). diff --git a/docs/concepts/overview/working-with-objects/labels.md b/docs/concepts/overview/working-with-objects/labels.md index 747a3bf561..b66085fca7 100644 --- a/docs/concepts/overview/working-with-objects/labels.md +++ b/docs/concepts/overview/working-with-objects/labels.md @@ -170,4 +170,4 @@ selector: #### Selecting sets of nodes One use case for selecting over labels is to constrain the set of nodes onto which a pod can schedule. -See the documentation on [node selection](/docs/user-guide/node-selection) for more information. +See the documentation on [node selection](/docs/concepts/configuration/assign-pods-nodes/) for more information. diff --git a/docs/concepts/workloads/controllers/replicaset.md b/docs/concepts/workloads/controllers/replicaset.md index 41194d8629..3a76afd128 100644 --- a/docs/concepts/workloads/controllers/replicaset.md +++ b/docs/concepts/workloads/controllers/replicaset.md @@ -119,7 +119,7 @@ for example the [Kubelet](/docs/admin/kubelet/) or Docker. ### Pod Selector -The `.spec.selector` field is a [label selector](/docs/user-guide/labels/#label-selectors). A ReplicaSet +The `.spec.selector` field is a [label selector](/docs/concepts/overview/working-with-objects/#label-selectors). A ReplicaSet manages all the pods with labels that match the selector. It does not distinguish between pods that it created or deleted and pods that another person or process created or deleted. This allows the ReplicaSet to be replaced without affecting the running pods. diff --git a/docs/getting-started-guides/binary_release.md b/docs/getting-started-guides/binary_release.md index ca1baf2c6d..452d301b33 100644 --- a/docs/getting-started-guides/binary_release.md +++ b/docs/getting-started-guides/binary_release.md @@ -57,4 +57,4 @@ Possible values for `YOUR_PROVIDER` include: * `vsphere` - VMWare VSphere * `rackspace` - Rackspace -For the complete, up-to-date list of providers supported by this script, see the [`/cluster`](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/cluster) folder in the main Kubernetes repo, where each folder represents a possible value for `YOUR_PROVIDER`. If you don't see your desired provider, try looking at our [getting started guides](/docs/getting-started-guides); there's a good chance we have docs for them. +For the complete, up-to-date list of providers supported by this script, see the [`/cluster`](https://github.com/kubernetes/kubernetes/tree/{{page.githubbranch}}/cluster) folder in the main Kubernetes repo, where each folder represents a possible value for `YOUR_PROVIDER`. If you don't see your desired provider, try looking at our [getting started guides](/docs/setup/); there's a good chance we have docs for them. diff --git a/docs/tasks/debug-application-cluster/debug-cluster.md b/docs/tasks/debug-application-cluster/debug-cluster.md index f522394a19..fc38c7269f 100644 --- a/docs/tasks/debug-application-cluster/debug-cluster.md +++ b/docs/tasks/debug-application-cluster/debug-cluster.md @@ -111,5 +111,5 @@ Mitigations: - Mitigates: Node shutdown - Mitigates: Kubelet software fault -- Action: [Multiple independent clusters](/docs/admin/multi-cluster) (and avoid making risky changes to all clusters at once) +- Action: [Multiple independent clusters](/docs/concepts/cluster-administration/federation/) (and avoid making risky changes to all clusters at once) - Mitigates: Everything listed above. diff --git a/docs/tutorials/stateful-application/zookeeper.md b/docs/tutorials/stateful-application/zookeeper.md index c1d7f6ae9e..e020b0e86c 100644 --- a/docs/tutorials/stateful-application/zookeeper.md +++ b/docs/tutorials/stateful-application/zookeeper.md @@ -89,7 +89,7 @@ safely discarded. The manifest below contains a [Headless Service](/docs/concepts/services-networking/service/#headless-services), -a [Service](/docs/concepts/services-networking/service), +a [Service](/docs/concepts/services-networking/service/), a [PodDisruptionBudget](/docs/concepts/workloads/pods/disruptions//#specifying-a-poddisruptionbudget), and a [StatefulSet](/docs/concepts/workloads/controllers/statefulset/).