Update links to avoid redirects. (#5614)

This commit is contained in:
Steve Perry
2017-09-25 10:04:09 -07:00
committed by GitHub
parent 8edb72657d
commit 35c7393849
103 changed files with 277 additions and 277 deletions
+1 -1
View File
@@ -504,7 +504,7 @@ This is commonly used by add-on API servers for unified authentication and autho
<tr>
<td><b>system:kube-dns</b></td>
<td><b>kube-dns</b> service account in the <b>kube-system</b> namespace</td>
<td>Role for the <a href="/docs/admin/dns/">kube-dns</a> component.</td>
<td>Role for the <a href="/docs/concepts/services-networking/dns-pod-service/">kube-dns</a> component.</td>
</tr>
<tr>
<td><b>system:node-bootstrapper</b></td>
+2 -2
View File
@@ -17,10 +17,10 @@ This guide explains how to set up cluster federation that lets us control multip
## Prerequisites
This guide assumes that you have a running Kubernetes cluster.
If you need to start a new cluster, see the [getting started guides](/docs/getting-started-guides/) for instructions on bringing a cluster up.
If you need to start a new cluster, see the [getting started guides](/docs/home/) for instructions on bringing a cluster up.
To use the commands in this guide, you must download a Kubernetes release from the
[getting started binary releases](/docs/getting-started-guides/binary_release/) and
[getting started binary releases](/docs/home/binary_release/) and
extract into a directory; all the commands in this guide are run from
that directory.
+1 -1
View File
@@ -6,7 +6,7 @@ title: Building High-Availability Clusters
This document describes how to build a high-availability (HA) Kubernetes cluster. This is a fairly advanced topic.
Users who merely want to experiment with Kubernetes are encouraged to use configurations that are simpler to set up such
as [Minikube](/docs/getting-started-guides/minikube/)
as [Minikube](/docs/home/minikube/)
or try [Google Container Engine](https://cloud.google.com/container-engine/) for hosted Kubernetes.
Also, at this time high availability support for Kubernetes is not continuously tested in our end-to-end (e2e) testing. We will