Update links to avoid redirects. (#5768)

docs/concepts/overview/what-is-kubernetes.md

@@ -121,7 +121,7 @@ The name **Kubernetes** originates from Greek, meaning *helmsman* or *pilot*, an
 {% endcapture %}
 
 {% capture whatsnext %}
-*   Ready to [Get Started](/docs/getting-started-guides/)?
+*   Ready to [Get Started](/docs/setup/)?
 *   For more details, see the [Kubernetes Documentation](/docs/home/).
 {% endcapture %}
 {% include templates/concept.md %}

docs/getting-started-guides/fedora/flannel_multi_node_cluster.md

@@ -191,8 +191,3 @@ IaaS Provider        | Config. Mgmt | OS     | Networking  | Docs
 Bare-metal           | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
 libvirt              | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
 KVM                  | custom       | Fedora | flannel     | [docs](/docs/getting-started-guides/fedora/flannel_multi_node_cluster/)      |          | Community ([@aveshagarwal](https://github.com/aveshagarwal))
-
-
-
-For support level information on all solutions, see the [Table of solutions](/docs/getting-started-guides/#table-of-solutions) chart.
-

docs/tasks/administer-federation/events.md

@@ -12,14 +12,14 @@ This guide explains how to use events in federation control plane to help in deb
 
 This guide assumes that you have a running Kubernetes Cluster
 Federation installation. If not, then head over to the
-[federation admin guide](/docs/admin/federation/) to learn how to
+[federation admin guide](/docs/concepts/cluster-administration/federation/) to learn how to
 bring up a cluster federation (or have your cluster administrator do
 this for you). Other tutorials, for example
 [this one](https://github.com/kelseyhightower/kubernetes-cluster-federation)
 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.
 
 ## Overview

docs/tasks/administer-federation/job.md

@@ -16,7 +16,7 @@ parallelism and completions 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 [jobs](/docs/concepts/workloads/controllers/jobs-run-to-completion/) in particular.
 {% endcapture %}
 

docs/tasks/debug-application-cluster/debug-stateful-set.md

@@ -44,7 +44,7 @@ You can debug individual Pods in a StatefulSet using the
 
 {% capture whatsnext %}
 
-Learn more about [debugging an init-container](/docs/tasks/troubleshoot/debug-init-containers/).
+Learn more about [debugging an init-container](/docs/tasks/debug-application-cluster/debug-init-containers/).
 
 {% endcapture %}
 

docs/tasks/federation/set-up-cluster-federation-kubefed.md

@@ -21,7 +21,7 @@ using `kubefed`.
 ## Prerequisites
 
 This guide assumes that you have a running Kubernetes cluster. Please
-see one of the [getting started](/docs/getting-started-guides/) guides
+see one of the [getting started](/docs/setup/) guides
 for installation instructions for your platform.
 
 
@@ -367,7 +367,7 @@ kubefed init fellowship \
 ```
 
 For more information see
-[Setting up CoreDNS as DNS provider for Cluster Federation](/docs/tutorials/federation/set-up-coredns-provider-federation/).
+[Setting up CoreDNS as DNS provider for Cluster Federation](/docs/tasks/federation/set-up-coredns-provider-federation/).
 
 ## Adding a cluster to a federation
 
@@ -383,7 +383,7 @@ for the federation control plane's host cluster.
 > Note: The name that you provide to the `join` command is used as the
 joining cluster's identity in federation. This name should adhere to
 the rules described in the
-[identifiers doc](/docs/user-guide/identifiers/#names). If the context
+[identifiers doc](docs/concepts/overview/working-with-objects/names/). If the context
 corresponding to your joining cluster conforms to these rules then you
 can use the same name in the join command. Otherwise, you will have to
 choose a different name for your cluster's identity. For more
@@ -408,7 +408,7 @@ cluster.
 
 The cluster name you supply to `kubefed join` must be a valid
 [RFC 1035](https://www.ietf.org/rfc/rfc1035.txt) label and are
-enumerated in the [Identifiers doc](/docs/user-guide/identifiers/#names).
+enumerated in the [Identifiers doc](docs/concepts/overview/working-with-objects/names/).
 
 Furthermore, federation control plane requires credentials of the
 joined clusters to operate on them. These credentials are obtained

docs/tasks/federation/set-up-placement-policies-federation.md

@@ -12,7 +12,7 @@ resources using an external policy engine.
 {% capture prerequisites %}
 
 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/)
+cluster). Please see one of the [getting started](/docs/setup/)
 guides for installation instructions for your platform.
 
 {% endcapture %}