Update links to avoid redirects. (#5827)

2017-10-09 19:17:59 -07:00
parent 11b0b64ab9
commit e830745509
15 changed files with 15 additions and 15 deletions
@@ -17,7 +17,7 @@ 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/setup/) 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 
@@ -8,7 +8,7 @@ title: Creating a Custom Cluster from Scratch

 This guide is for people who want to craft a custom Kubernetes cluster.  If you
 can find an existing Getting Started Guide that meets your needs on [this
-list](/docs/getting-started-guides/), then we recommend using it, as you will be able to benefit
+list](/docs/setup/), then we recommend using it, as you will be able to benefit
 from the experience of others.  However, if you have specific IaaS, networking,
 configuration management, or operating system requirements not met by any of
 those guides, then this guide will provide an outline of the steps you need to
@@ -14,7 +14,7 @@ Kubernetes CLI, `kubectl`.

 To access a cluster, you need to know the location of the cluster and have credentials
 to access it.  Typically, this is automatically set-up when you work through
-a [Getting started guide](/docs/getting-started-guides/),
+a [Getting started guide](/docs/setup/),
 or someone else setup the cluster and provided you with credentials and a location.

 Check the location and credentials that kubectl knows about with this command:
@@ -22,7 +22,7 @@ Kubernetes command-line tool, `kubectl`.

 To access a cluster, you need to know the location of the cluster and have credentials
 to access it.  Typically, this is automatically set-up when you work through
-a [Getting started guide](/docs/getting-started-guides/),
+a [Getting started guide](/docs/setup/),
 or someone else setup the cluster and provided you with credentials and a location.

 Check the location and credentials that kubectl knows about with this command:
@@ -15,7 +15,7 @@ running cluster.

 ## Creating and configuring a Cluster

-To install Kubernetes on a set of machines, consult one of the existing [Getting Started guides](/docs/getting-started-guides/) depending on your environment.
+To install Kubernetes on a set of machines, consult one of the existing [Getting Started guides](/docs/setup/) depending on your environment.

 ## Upgrading a cluster

@@ -20,7 +20,7 @@ This example demonstrates how to use Kubernetes namespaces to subdivide your clu

 This example assumes the following:

-1. You have an [existing Kubernetes cluster](/docs/getting-started-guides/).
+1. You have an [existing Kubernetes cluster](/docs/setup/).
 2. You have a basic understanding of Kubernetes _[Pods](/docs/concepts/workloads/pods/pod/)_, _[Services](/docs/concepts/services-networking/service/)_, and _[Deployments](/docs/concepts/workloads/controllers/deployment/)_.

 ### Step One: Understand the default namespace
@@ -10,7 +10,7 @@ This page shows how to view, work in, and delete namespaces. The page also shows
 {% endcapture %}

 {% capture prerequisites %}
-* Have an [existing Kubernetes cluster](/docs/getting-started-guides/).
+* Have an [existing Kubernetes cluster](/docs/setup/).
 * Have a basic understanding of Kubernetes _[Pods](/docs/concepts/workloads/pods/pod/)_, _[Services](/docs/concepts/services-networking/service/)_, and _[Deployments](/docs/concepts/workloads/controllers/deployment/)_.
 {% endcapture %}

@@ -66,7 +66,7 @@ this for you). Other tutorials, for example
 by Kelsey Hightower, are also available to help you.

 You must also have a basic
-[working knowledge of Kubernetes](/docs/getting-started-guides/) in
+[working knowledge of Kubernetes](/docs/setup/) in
 general, and [Ingress](/docs/concepts/services-networking/ingress/) in particular.
 {% endcapture %}

@@ -16,7 +16,7 @@ replicas exist across the registered clusters.

 * {% include federated-task-tutorial-prereqs.md %}
 * You are also expected to have a basic
-[working knowledge of Kubernetes](/docs/getting-started-guides/) in
+[working knowledge of Kubernetes](/docs/setup/) in
 general and [ReplicaSets](/docs/concepts/workloads/controllers/replicaset/) in particular.
 {% endcapture %}

@@ -18,7 +18,7 @@ this for you). Other tutorials, for example
 by Kelsey Hightower, are also available to help you.

 You are also expected to have a basic
-[working knowledge of Kubernetes](/docs/getting-started-guides/) in
+[working knowledge of Kubernetes](/docs/setup/) in
 general and [Secrets](/docs/concepts/configuration/secret/) in particular.

 ## Overview
@@ -25,7 +25,7 @@ this for you). Other tutorials, for example
 by Kelsey Hightower, are also available to help you.

 You are also expected to have a basic
-[working knowledge of Kubernetes](/docs/getting-started-guides/) in
+[working knowledge of Kubernetes](/docs/setup/) in
 general, and [Services](/docs/concepts/services-networking/service/) in particular.

 ## Overview
@@ -23,7 +23,7 @@ DNS provider for Cluster Federation.

 * You need to have a running Kubernetes cluster (which is
 referenced as host cluster). Please see one of the
-[getting started](/docs/getting-started-guides/) guides for
+[getting started](/docs/setup/) guides for
 installation instructions for your platform.
 * Support for `LoadBalancer` services in member clusters of federation is
 mandatory to enable `CoreDNS` for service discovery across federated clusters.
@@ -141,7 +141,7 @@ $ kubectl exec -ti nginx-app-5jyvm -- /bin/sh
 # exit
 ```

-For more information see [Getting a Shell to a Running Container](/docs/tasks/kubectl/get-shell-running-container/).
+For more information see [Getting a Shell to a Running Container](/docs/tasks/debug-application-cluster/get-shell-running-container/).

 #### docker logs

@@ -11,7 +11,7 @@ here](https://github.com/kubernetes/kubernetes.github.io/tree/{{page.docsbranch}

 ### Step Zero: Prerequisites

-This example assumes that you have forked the docs repository and [turned up a Kubernetes cluster](/docs/getting-started-guides/):
+This example assumes that you have forked the docs repository and [turned up a Kubernetes cluster](/docs/setup/):

 ```shell
 $ git clone -b {{page.docsbranch}} https://github.com/kubernetes/kubernetes.github.io
@@ -57,7 +57,7 @@ List all pods:
 $ kubectl get pods
 ```

-On most providers, the pod IPs are not externally accessible. The easiest way to test that the pod is working is to create a busybox pod and exec commands on it remotely. See the [command execution documentation](/docs/tasks/kubectl/get-shell-running-container/) for details.
+On most providers, the pod IPs are not externally accessible. The easiest way to test that the pod is working is to create a busybox pod and exec commands on it remotely. See the [command execution documentation](/docs/tasks/debug-application-cluster/get-shell-running-container/) for details.

 Provided the pod IP is accessible, you should be able to access its http endpoint with wget on port 80: