Update links to avoid redirects. (#5771)

docs/concepts/cluster-administration/cluster-administration-overview.md

@@ -7,7 +7,7 @@ title: Cluster Administration Overview
 
 {% capture overview %}
 The cluster administration overview is for anyone creating or administering a Kubernetes cluster.
-It assumes some familiarity with concepts in the [User Guide](/docs/user-guide/).
+It assumes some familiarity with core Kubernetes [concepts](/docs/concepts/).
 {% endcapture %}
 
 {% capture body %}
@@ -18,7 +18,7 @@ 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/concepts/cluster-administration/federation/).
  - 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/concepts/cluster-administration/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.

docs/concepts/configuration/secret.md

@@ -37,7 +37,7 @@ The automatic creation and use of API credentials can be disabled or overridden
 if desired.  However, if all you need to do is securely access the apiserver,
 this is the recommended workflow.
 
-See the [Service Account](/docs/user-guide/service-accounts) documentation for more
+See the [Service Account](/docs/tasks/configure-pod-container/configure-service-account/) documentation for more
 information on how Service Accounts work.
 
 ### Creating your own Secrets
@@ -406,7 +406,7 @@ See [Adding ImagePullSecrets to a service account](/docs/tasks/configure-pod-con
 
 Manually created secrets (e.g. one containing a token for accessing a github account)
 can be automatically attached to pods based on their service account.
-See [Injecting Information into Pods Using a PodPreset](/docs/tasks/run-application/podpreset/) for a detailed explanation of that process.
+See [Injecting Information into Pods Using a PodPreset](/docs/tasks/inject-data-application/podpreset/) for a detailed explanation of that process.
 
 ## Details
 

docs/concepts/services-networking/connect-applications-service.md

@@ -168,7 +168,7 @@ Till now we have only accessed the nginx server from within the cluster. Before
 
 * Self signed certificates for https (unless you already have an identity certificate)
 * An nginx server configured to use the certificates
-* A [secret](/docs/user-guide/secrets) that makes the certificates accessible to pods
+* A [secret](/docs/concepts/configuration/secret/) that makes the certificates accessible to pods
 
 You can acquire all these from the [nginx https example](https://github.com/kubernetes/examples/tree/{{page.githubbranch}}/staging/https-nginx/), in short:
 
@@ -296,7 +296,3 @@ clusters and cloud providers, to provide increased availability,
 better fault tolerance and greater scalability for your services. See
 the [Federated Services User Guide](/docs/concepts/cluster-administration/federation-service-discovery/)
 for further information.
-
-## What's next?
-
-[Learn about more Kubernetes features that will help you run containers reliably in production.](/docs/user-guide/production-pods)