From e8307455092daddcc65b240a2210110a30278652 Mon Sep 17 00:00:00 2001 From: Steve Perry Date: Mon, 9 Oct 2017 19:17:59 -0700 Subject: [PATCH] Update links to avoid redirects. (#5827) --- docs/admin/federation/index.md | 2 +- docs/getting-started-guides/scratch.md | 2 +- docs/tasks/access-application-cluster/access-cluster.md | 2 +- docs/tasks/administer-cluster/access-cluster-api.md | 2 +- docs/tasks/administer-cluster/cluster-management.md | 2 +- docs/tasks/administer-cluster/namespaces-walkthrough.md | 2 +- docs/tasks/administer-cluster/namespaces.md | 2 +- docs/tasks/administer-federation/ingress.md | 2 +- docs/tasks/administer-federation/replicaset.md | 2 +- docs/tasks/administer-federation/secret.md | 2 +- docs/tasks/federation/federation-service-discovery.md | 2 +- docs/tasks/federation/set-up-coredns-provider-federation.md | 2 +- docs/user-guide/docker-cli-to-kubectl.md | 2 +- docs/user-guide/update-demo/index.md.orig | 2 +- docs/user-guide/walkthrough/index.md | 2 +- 15 files changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/admin/federation/index.md b/docs/admin/federation/index.md index d4c524a926..363bd25fe6 100644 --- a/docs/admin/federation/index.md +++ b/docs/admin/federation/index.md @@ -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 diff --git a/docs/getting-started-guides/scratch.md b/docs/getting-started-guides/scratch.md index df4a7318d3..d03e813199 100644 --- a/docs/getting-started-guides/scratch.md +++ b/docs/getting-started-guides/scratch.md @@ -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 diff --git a/docs/tasks/access-application-cluster/access-cluster.md b/docs/tasks/access-application-cluster/access-cluster.md index 26c13179ef..29e6e08393 100644 --- a/docs/tasks/access-application-cluster/access-cluster.md +++ b/docs/tasks/access-application-cluster/access-cluster.md @@ -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: diff --git a/docs/tasks/administer-cluster/access-cluster-api.md b/docs/tasks/administer-cluster/access-cluster-api.md index 0be8784993..83738368aa 100644 --- a/docs/tasks/administer-cluster/access-cluster-api.md +++ b/docs/tasks/administer-cluster/access-cluster-api.md @@ -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: diff --git a/docs/tasks/administer-cluster/cluster-management.md b/docs/tasks/administer-cluster/cluster-management.md index a1d8037c85..17b509c372 100644 --- a/docs/tasks/administer-cluster/cluster-management.md +++ b/docs/tasks/administer-cluster/cluster-management.md @@ -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 diff --git a/docs/tasks/administer-cluster/namespaces-walkthrough.md b/docs/tasks/administer-cluster/namespaces-walkthrough.md index e327f20577..7415b490ac 100644 --- a/docs/tasks/administer-cluster/namespaces-walkthrough.md +++ b/docs/tasks/administer-cluster/namespaces-walkthrough.md @@ -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 diff --git a/docs/tasks/administer-cluster/namespaces.md b/docs/tasks/administer-cluster/namespaces.md index 2b26e846d3..bedaec6d2c 100644 --- a/docs/tasks/administer-cluster/namespaces.md +++ b/docs/tasks/administer-cluster/namespaces.md @@ -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 %} diff --git a/docs/tasks/administer-federation/ingress.md b/docs/tasks/administer-federation/ingress.md index 7909063543..69d0f22f02 100644 --- a/docs/tasks/administer-federation/ingress.md +++ b/docs/tasks/administer-federation/ingress.md @@ -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 %} diff --git a/docs/tasks/administer-federation/replicaset.md b/docs/tasks/administer-federation/replicaset.md index 896442b35b..d36b2038df 100644 --- a/docs/tasks/administer-federation/replicaset.md +++ b/docs/tasks/administer-federation/replicaset.md @@ -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 %} diff --git a/docs/tasks/administer-federation/secret.md b/docs/tasks/administer-federation/secret.md index 2cd9aa26ea..5c07854dbb 100644 --- a/docs/tasks/administer-federation/secret.md +++ b/docs/tasks/administer-federation/secret.md @@ -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 diff --git a/docs/tasks/federation/federation-service-discovery.md b/docs/tasks/federation/federation-service-discovery.md index bd6fa501a5..35df2b7d4a 100644 --- a/docs/tasks/federation/federation-service-discovery.md +++ b/docs/tasks/federation/federation-service-discovery.md @@ -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 diff --git a/docs/tasks/federation/set-up-coredns-provider-federation.md b/docs/tasks/federation/set-up-coredns-provider-federation.md index ed2cc57189..aead3266ec 100644 --- a/docs/tasks/federation/set-up-coredns-provider-federation.md +++ b/docs/tasks/federation/set-up-coredns-provider-federation.md @@ -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. diff --git a/docs/user-guide/docker-cli-to-kubectl.md b/docs/user-guide/docker-cli-to-kubectl.md index 2f4b4b7948..326cf6e019 100644 --- a/docs/user-guide/docker-cli-to-kubectl.md +++ b/docs/user-guide/docker-cli-to-kubectl.md @@ -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 diff --git a/docs/user-guide/update-demo/index.md.orig b/docs/user-guide/update-demo/index.md.orig index c6fbc3bf8c..77af52f62c 100644 --- a/docs/user-guide/update-demo/index.md.orig +++ b/docs/user-guide/update-demo/index.md.orig @@ -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 diff --git a/docs/user-guide/walkthrough/index.md b/docs/user-guide/walkthrough/index.md index ae5a938ec9..89fba268ee 100644 --- a/docs/user-guide/walkthrough/index.md +++ b/docs/user-guide/walkthrough/index.md @@ -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: