Revert "Update links to avoid redirects." (#5617)

* Revert "Fix the doc example"

This reverts commit 2872def62b.

* Revert "add the set of sessionAffinity timeoutseconds (#5474)"

This reverts commit 657734de6f.

* Revert "pod-security-policy.md: fix broken link to PSP proposal."

This reverts commit 8db51e099f.

* Revert "fix typo"

This reverts commit 24e5383071.

* Revert "Update images.md"

This reverts commit f844a41502.

* Revert "Update links to avoid redirects. (#5614)"

This reverts commit 35c7393849.

docs/concepts/workloads/pods/disruptions.md

@@ -72,7 +72,7 @@ Here are some ways to mitigate involuntary disruptions:
 and [stateful](/docs/tasks/run-application/run-replicated-stateful-application/) applications.)
 - For even higher availability when running replicated applications,
 spread applications across racks (using
-[anti-affinity](/docs/concepts/configuration/assign-pod-node//#inter-pod-affinity-and-anti-affinity-beta-feature))
+[anti-affinity](/docs/user-guide/node-selection/#inter-pod-affinity-and-anti-affinity-beta-feature))
 or across zones (if using a
 [multi-zone cluster](/docs/admin/multiple-zones).)
 

docs/concepts/workloads/pods/init-containers.md

@@ -87,7 +87,7 @@ Here are some ideas for how to use Init Containers:
   place the POD_IP value in a configuration and generate the main app
   configuration file using Jinja.
 
-More detailed usage examples can be found in the [StatefulSets documentation](/docs/concepts/workloads/controllers/statefulset/)
+More detailed usage examples can be found in the [StatefulSets documentation](/docs/concepts/abstractions/controllers/statefulsets/)
 and the [Production Pods guide](/docs/tasks/#handling-initialization).
 
 ### Init Containers in use

docs/concepts/workloads/pods/pod-overview.md

@@ -64,7 +64,7 @@ A Controller can create and manage multiple Pods for you, handling replication a
 Some examples of Controllers that contain one or more pods include:
 
 * [Deployment](/docs/concepts/workloads/controllers/deployment/)
-* [StatefulSet](/docs/concepts/workloads/controllers/statefulset/)
+* [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets/)
 * [DaemonSet](/docs/concepts/workloads/controllers/daemonset/)
 
 In general, Controllers use a Pod Template that you provide to create the Pods for which it is responsible.

docs/concepts/workloads/pods/pod.md

@@ -150,7 +150,7 @@ Pod is exposed as a primitive in order to facilitate:
 * clean composition of Kubelet-level functionality with cluster-level functionality — Kubelet is effectively the "pod controller"
 * high-availability applications, which will expect pods to be replaced in advance of their termination and certainly in advance of deletion, such as in the case of planned evictions, image prefetching, or live pod migration [#3949](http://issue.k8s.io/3949)
 
-There is new first-class support for stateful pods with the [StatefulSet](/docs/concepts/workloads/controllers/statefulset/) controller (currently in beta). The feature was alpha in 1.4 and was called [PetSet](/docs/concepts/workloads/controllers/petset/). For prior versions of Kubernetes, best practice for having stateful pods is to create a replication controller with `replicas` equal to `1` and a corresponding service, see [this MySQL deployment example](/docs/tutorials/stateful-application/run-stateful-application/).
+There is new first-class support for stateful pods with the [StatefulSet](/docs/concepts/abstractions/controllers/statefulsets/) controller (currently in beta). The feature was alpha in 1.4 and was called [PetSet](/docs/concepts/workloads/controllers/petset/). For prior versions of Kubernetes, best practice for having stateful pods is to create a replication controller with `replicas` equal to `1` and a corresponding service, see [this MySQL deployment example](/docs/tutorials/stateful-application/run-stateful-application/).
 
 ## Termination of Pods