Add trailing slashes to reduce redirects. (#5592)

2017-09-23 03:41:18 -07:00
parent ed5d92d91e
commit 9b31b9a4d3
17 changed files with 124 additions and 124 deletions
@@ -13,7 +13,7 @@ This section describes all the possible configurations which can
 be used when running Kubernetes on Amazon Web Services.

 ## Load Balancers
-You can setup [external load balancers](/docs/tasks/access-application-cluster/create-external-load-balancer)
+You can setup [external load balancers](/docs/tasks/access-application-cluster/create-external-load-balancer/)
 to use specific features in AWS by configuring the annotations as shown below.

 ```yaml
@@ -18,23 +18,23 @@ See the guides in [Picking the Right Solution](/docs/setup/pick-right-solution/)
 Before choosing a guide, here are some considerations:

 - Do you just want to try out Kubernetes on your computer, or do you want to build a high-availability, multi-node cluster? Choose distros best suited for your needs.
- - **If you are designing for high-availability**, learn about configuring [clusters in multiple zones](/docs/admin/multi-cluster).
+ - **If you are designing for high-availability**, learn about configuring [clusters in multiple zones](/docs/admin/multi-cluster/).
 - Will you be using **a hosted Kubernetes cluster**, such as [Google Container Engine (GKE)](https://cloud.google.com/container-engine/), or **hosting your own cluster**?
 - Will your cluster be **on-premises**, or **in the cloud (IaaS)**? Kubernetes does not directly support hybrid clusters. Instead, you can set up multiple clusters.
- - **If you are configuring Kubernetes on-premises**, consider which [networking model](/docs/admin/networking) fits best. One option for custom networking is [*OpenVSwitch GRE/VxLAN networking*](/docs/admin/ovs-networking/), which uses OpenVSwitch to set up networking between pods across Kubernetes nodes.
+ - **If you are configuring Kubernetes on-premises**, consider which [networking model](/docs/admin/networking/) fits best. One option for custom networking is [*OpenVSwitch GRE/VxLAN networking*](/docs/admin/ovs-networking/), which uses OpenVSwitch to set up networking between pods across Kubernetes nodes.
 - Will you be running Kubernetes on **"bare metal" hardware** or on **virtual machines (VMs)**?
 - Do you **just want to run a cluster**, or do you expect to do **active development of Kubernetes project code**? If the
   latter, choose a actively-developed distro. Some distros only use binary releases, but
   offer a greater variety of choices.
- - Familiarize yourself with the [components](/docs/admin/cluster-components) needed to run a cluster.
+ - Familiarize yourself with the [components](/docs/admin/cluster-components/) needed to run a cluster.

 Note: Not all distros are actively maintained. Choose distros which have been tested with a recent version of Kubernetes.

-If you are using a guide involving Salt, see [Configuring Kubernetes with Salt](/docs/admin/salt).
+If you are using a guide involving Salt, see [Configuring Kubernetes with Salt](/docs/admin/salt/).

 ## Managing a cluster

-* [Managing a cluster](/docs/concepts/cluster-administration/cluster-management/) describes several topics related to the lifecycle of a cluster: creating a new cluster, upgrading your cluster’s master and worker nodes, performing node maintenance (e.g. kernel upgrades), and upgrading the Kubernetes API version of a running cluster..
+* [Managing a cluster](/docs/concepts/cluster-administration/cluster-management/) describes several topics related to the lifecycle of a cluster: creating a new cluster, upgrading your cluster’s master and worker nodes, performing node maintenance (e.g. kernel upgrades), and upgrading the Kubernetes API version of a running cluster.

 * Learn how to [manage nodes](/docs/concepts/nodes/node/).

@@ -44,13 +44,13 @@ If you are using a guide involving Salt, see [Configuring Kubernetes with Salt](

 * [Kubernetes Container Environment](/docs/concepts/containers/container-environment-variables/) describes the environment for Kubelet managed containers on a Kubernetes node.

-* [Controlling Access to the Kubernetes API](/docs/admin/accessing-the-api) describes how to set up permissions for users and service accounts.
+* [Controlling Access to the Kubernetes API](/docs/admin/accessing-the-api/) describes how to set up permissions for users and service accounts.

-* [Authenticating](/docs/admin/authentication) explains authentication in Kubernetes, including the various authentication options.
+* [Authenticating](/docs/admin/authentication/) explains authentication in Kubernetes, including the various authentication options.

-* [Authorization](/docs/admin/authorization) is separate from authentication, and controls how HTTP calls are handled.
+* [Authorization](/docs/admin/authorization/) is separate from authentication, and controls how HTTP calls are handled.

-* [Using Admission Controllers](/docs/admin/admission-controllers) explains plug-ins which intercepts requests to the Kubernetes API server after authentication and authorization.
+* [Using Admission Controllers](/docs/admin/admission-controllers/) explains plug-ins which intercepts requests to the Kubernetes API server after authentication and authorization.

 * [Using Sysctls in a Kubernetes Cluster](/docs/concepts/cluster-administration/sysctl-cluster/) describes to an administrator how to use the `sysctl` command-line tool to set kernel parameters .

@@ -19,7 +19,7 @@ This page describes the resources available to Containers in the Container envir

 The Kubernetes Container environment provides several important resources to Containers:

-* A filesystem, which is a combination of an [image](/docs/concepts/containers/images) and one or more [volumes](/docs/concepts/storage/volumes).
+* A filesystem, which is a combination of an [image](/docs/concepts/containers/images/) and one or more [volumes](/docs/concepts/storage/volumes/).
 * Information about the Container itself.
 * Information about other objects in the cluster.

@@ -31,7 +31,7 @@ It is available through the `hostname` command or the
 function call in libc.

 The Pod name and namespace are available as environment variables through the
-[downward API](/docs/tasks/configure-pod-container/downward-api-volume-expose-pod-information).
+[downward API](/docs/tasks/configure-pod-container/downward-api-volume-expose-pod-information/).

 User defined environment variables from the Pod definition are also available to the Container,
 as are any environment variables specified statically in the Docker image.
@@ -18,20 +18,20 @@ cluster (for example, scheduling), and detecting and responding to cluster event
 Master components can be run on any node in the cluster. However,
 for simplicity, set up scripts typically start all master components on
 the same VM, and do not run user containers on this VM. See
-[Building High-Availability Clusters](/docs/admin/high-availability) for an example multi-master-VM setup.
+[Building High-Availability Clusters](/docs/admin/high-availability/) for an example multi-master-VM setup.

 ### kube-apiserver

-[kube-apiserver](/docs/admin/kube-apiserver) exposes the Kubernetes API. It is the front-end for the
-Kubernetes control plane. It is designed to scale horizontally -- that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability).
+[kube-apiserver](/docs/admin/kube-apiserver/) exposes the Kubernetes API. It is the front-end for the
+Kubernetes control plane. It is designed to scale horizontally -- that is, it scales by deploying more instances. See [Building High-Availability Clusters](/docs/admin/high-availability/).

 ### etcd

-[etcd](/docs/tasks/administer-cluster/configure-upgrade-etcd) is used as Kubernetes' backing store. All cluster data is stored here. Always have a backup plan for etcd's data for your Kubernetes cluster.
+[etcd](/docs/tasks/administer-cluster/configure-upgrade-etcd/) is used as Kubernetes' backing store. All cluster data is stored here. Always have a backup plan for etcd's data for your Kubernetes cluster.

 ### kube-controller-manager

-[kube-controller-manager](/docs/admin/kube-controller-manager) runs controllers, which are the background threads that handle routine tasks in the cluster. Logically, each controller is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process.
+[kube-controller-manager](/docs/admin/kube-controller-manager/) runs controllers, which are the background threads that handle routine tasks in the cluster. Logically, each controller is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process.

 These controllers include:

@@ -58,7 +58,7 @@ The following controllers have cloud provider dependencies:

 ### kube-scheduler

-[kube-scheduler](/docs/admin/kube-scheduler) watches newly created pods that have no node assigned, and
+[kube-scheduler](/docs/admin/kube-scheduler/) watches newly created pods that have no node assigned, and
 selects a node for them to run on.

 ### addons
@@ -84,12 +84,12 @@ Containers started by Kubernetes automatically include this DNS server in their

 #### Container Resource Monitoring

-[Container Resource Monitoring](/docs/tasks/debug-application-cluster/resource-usage-monitoring) records generic time-series metrics
+[Container Resource Monitoring](/docs/tasks/debug-application-cluster/resource-usage-monitoring/) records generic time-series metrics
 about containers in a central database, and provides a UI for browsing that data.

 #### Cluster-level Logging

-A [Cluster-level logging](/docs/concepts/cluster-administration/logging) mechanism is responsible for
+A [Cluster-level logging](/docs/concepts/cluster-administration/logging/) mechanism is responsible for
 saving container logs to a central log store with search/browsing interface.

 ## Node components
@@ -98,7 +98,7 @@ Node components run on every node, maintaining running pods and providing the Ku

 ### kubelet

-[kubelet](/docs/admin/kubelet) is the primary node agent. It watches for pods that have been assigned to its node (either by apiserver or via local configuration file) and:
+[kubelet](/docs/admin/kubelet/) is the primary node agent. It watches for pods that have been assigned to its node (either by apiserver or via local configuration file) and:

  * Mounts the pod's required volumes.
  * Downloads the pod's secrets.
@@ -109,7 +109,7 @@ Node components run on every node, maintaining running pods and providing the Ku

 ### kube-proxy

-[kube-proxy](/docs/admin/kube-proxy) enables the Kubernetes service abstraction by maintaining
+[kube-proxy](/docs/admin/kube-proxy/) enables the Kubernetes service abstraction by maintaining
 network rules on the host and performing connection forwarding.


@@ -160,7 +160,7 @@ The StatefulSet should not specify a `pod.Spec.TerminationGracePeriodSeconds` of

 When the nginx example above is created, three Pods will be deployed in the order
 web-0, web-1, web-2. web-1 will not be deployed before web-0 is
-[Running and Ready](/docs/user-guide/pod-states), and web-2 will not be deployed until
+[Running and Ready](/docs/user-guide/pod-states/), and web-2 will not be deployed until
 web-1 is Running and Ready. If web-0 should fail, after web-1 is Running and Ready, but before
 web-2 is launched, web-2 will not be launched until web-0 is successfully relaunched and
 becomes Running and Ready.
@@ -225,7 +225,7 @@ update, roll out a canary, or perform a phased roll out.
 {% endcapture %}
 {% capture whatsnext %}

-* Follow an example of [deploying a stateful application](/docs/tutorials/stateful-application/basic-stateful-set).
+* Follow an example of [deploying a stateful application](/docs/tutorials/stateful-application/basic-stateful-set/).
 * Follow an example of [deploying Cassandra with Stateful Sets](/docs/tutorials/stateful-application/cassandra/).

 {% endcapture %}