Fix redirections for generated api references (#7890)

We have been using redirections in many pages when referencing the API
docs generated. Since the relocation of the generated files, this is
becoming difficult to maintain. This PR redirects all such links to the
generated artifacts so we can easily detect missing links if any.

closes: #7874

docs/tasks/configure-pod-container/assign-cpu-resource.md

@@ -225,7 +225,7 @@ could use all of the CPU resources available on the Node where it is running.
 
 * The Container is running in a namespace that has a default CPU limit, and the
 Container is automatically assigned the default limit. Cluster administrators can use a
-[LimitRange](https://kubernetes.io/docs/api-reference/{{page.version}}/#limitrange-v1-core/)
+[LimitRange](/docs/reference/generated/kubernetes-api/{{page.version}}/#limitrange-v1-core/)
 to specify a default value for the CPU limit.
 
 ## Motivation for CPU requests and limits

docs/tasks/configure-pod-container/assign-memory-resource.md

@@ -321,7 +321,7 @@ could use all of the memory available on the Node where it is running.
 
 * The Container is running in a namespace that has a default memory limit, and the
 Container is automatically assigned the default limit. Cluster administrators can use a
-[LimitRange](https://kubernetes.io/docs/api-reference/{{page.version}}/#limitrange-v1-core)
+[LimitRange](/docs/reference/generated/kubernetes-api/{{page.version}}/#limitrange-v1-core)
 to specify a default value for the memory limit.
 
 ## Motivation for memory requests and limits

docs/tasks/configure-pod-container/attach-handler-lifecycle-event.md

@@ -90,9 +90,9 @@ This limitation is tracked in [issue #55087](https://github.com/kubernetes/kuber
 
 ### Reference
 
-* [Lifecycle](/docs/api-reference/{{page.version}}/#lifecycle-v1-core)
-* [Container](/docs/api-reference/{{page.version}}/#container-v1-core)
-* See `terminationGracePeriodSeconds` in [PodSpec](/docs/api-reference/{{page.version}}/#podspec-v1-core)
+* [Lifecycle](/docs/reference/generated/kubernetes-api/{{page.version}}/#lifecycle-v1-core)
+* [Container](/docs/reference/generated/kubernetes-api/{{page.version}}/#container-v1-core)
+* See `terminationGracePeriodSeconds` in [PodSpec](/docs/reference/generated/kubernetes-api/{{page.version}}/#podspec-v1-core)
 
 {% endcapture %}
 

docs/tasks/configure-pod-container/configure-liveness-readiness-probes.md

@@ -196,7 +196,7 @@ will be restarted.
 ## Use a named port
 
 You can use a named
-[ContainerPort](/docs/api-reference/{{page.version}}/#containerport-v1-core)
+[ContainerPort](/docs/reference/generated/kubernetes-api/{{page.version}}/#containerport-v1-core)
 for HTTP or TCP liveness checks:
 
 ```yaml
@@ -247,7 +247,7 @@ for it, and that containers are restarted when they fail.
 Eventually, some of this section could be moved to a concept topic.
 {% endcomment %}
 
-[Probes](/docs/api-reference/{{page.version}}/#probe-v1-core) have a number of fields that
+[Probes](/docs/reference/generated/kubernetes-api/{{page.version}}/#probe-v1-core) have a number of fields that
 you can use to more precisely control the behavior of liveness and readiness
 checks:
 
@@ -264,7 +264,7 @@ liveness. Minimum value is 1.
 try `failureThreshold` times before giving up. Giving up in case of liveness probe means restarting the Pod. In case of readiness probe the Pod will be marked Unready.
 Defaults to 3. Minimum value is 1.
 
-[HTTP probes](/docs/api-reference/{{page.version}}/#httpgetaction-v1-core)
+[HTTP probes](/docs/reference/generated/kubernetes-api/{{page.version}}/#httpgetaction-v1-core)
 have additional fields that can be set on `httpGet`:
 
 * `host`: Host name to connect to, defaults to the pod IP. You probably want to
@@ -294,9 +294,9 @@ case, you should not use `host`, but rather set the `Host` header in `httpHeader
 
 ### Reference
 
-* [Pod](/docs/api-reference/{{page.version}}/#pod-v1-core)
-* [Container](/docs/api-reference/{{page.version}}/#container-v1-core)
-* [Probe](/docs/api-reference/{{page.version}}/#probe-v1-core)
+* [Pod](/docs/reference/generated/kubernetes-api/{{page.version}}/#pod-v1-core)
+* [Container](/docs/reference/generated/kubernetes-api/{{page.version}}/#container-v1-core)
+* [Probe](/docs/reference/generated/kubernetes-api/{{page.version}}/#probe-v1-core)
 
 {% endcapture %}
 

docs/tasks/configure-pod-container/configure-persistent-volume-storage.md

@@ -54,7 +54,7 @@ PersistentVolume uses a file or directory on the Node to emulate network-attache
 In a production cluster, you would not use hostPath. Instead a cluster administrator
 would provision a network resource like a Google Compute Engine persistent disk,
 an NFS share, or an Amazon Elastic Block Store volume. Cluster administrators can also
-use [StorageClasses](/docs/api-reference/{{page.version}}/#storageclass-v1-storage)
+use [StorageClasses](/docs/reference/generated/kubernetes-api/{{page.version}}/#storageclass-v1-storage)
 to set up
 [dynamic provisioning](http://blog.kubernetes.io/2016/10/dynamic-provisioning-and-storage-in-kubernetes.html).
 
@@ -200,10 +200,10 @@ PersistentVolume are not present on the Pod resource itself.
 
 ### Reference
 
-* [PersistentVolume](/docs/api-reference/{{page.version}}/#persistentvolume-v1-core)
-* [PersistentVolumeSpec](/docs/api-reference/{{page.version}}/#persistentvolumespec-v1-core)
-* [PersistentVolumeClaim](/docs/api-reference/{{page.version}}/#persistentvolumeclaim-v1-core)
-* [PersistentVolumeClaimSpec](/docs/api-reference/{{page.version}}/#persistentvolumeclaimspec-v1-core)
+* [PersistentVolume](/docs/reference/generated/kubernetes-api/{{page.version}}/#persistentvolume-v1-core)
+* [PersistentVolumeSpec](/docs/reference/generated/kubernetes-api/{{page.version}}/#persistentvolumespec-v1-core)
+* [PersistentVolumeClaim](/docs/reference/generated/kubernetes-api/{{page.version}}/#persistentvolumeclaim-v1-core)
+* [PersistentVolumeClaimSpec](/docs/reference/generated/kubernetes-api/{{page.version}}/#persistentvolumeclaimspec-v1-core)
 
 {% endcapture %}
 

docs/tasks/configure-pod-container/configure-volume-storage.md

@@ -83,7 +83,7 @@ you will see something like this:
 
 At this point, the Container has terminated and restarted. This is because the
 redis Pod has a
-[restartPolicy](/docs/api-reference/{{page.version}}/#podspec-v1-core)
+[restartPolicy](/docs/reference/generated/kubernetes-api/{{page.version}}/#podspec-v1-core)
 of `Always`.
 
 1. Get a shell into the restarted Container:
@@ -96,9 +96,9 @@ of `Always`.
 
 {% capture whatsnext %}
 
-* See [Volume](/docs/api-reference/{{page.version}}/#volume-v1-core).
+* See [Volume](/docs/reference/generated/kubernetes-api/{{page.version}}/#volume-v1-core).
 
-* See [Pod](/docs/api-reference/{{page.version}}/#pod-v1-core).
+* See [Pod](/docs/reference/generated/kubernetes-api/{{page.version}}/#pod-v1-core).
 
 * In addition to the local disk storage provided by `emptyDir`, Kubernetes
 supports many different network-attached storage solutions, including PD on

docs/tasks/configure-pod-container/pull-image-private-registry.md

@@ -126,8 +126,8 @@ Create a Pod that uses your Secret, and verify that the Pod is running:
 * Learn more about [Secrets](/docs/concepts/configuration/secret/).
 * Learn more about [using a private registry](/docs/concepts/containers/images/#using-a-private-registry).
 * See [kubectl create secret docker-registry](/docs/user-guide/kubectl/{{page.version}}/#-em-secret-docker-registry-em-).
-* See [Secret](/docs/api-reference/{{page.version}}/#secret-v1-core).
-* See the `imagePullSecrets` field of [PodSpec](/docs/api-reference/{{page.version}}/#podspec-v1-core).
+* See [Secret](/docs/reference/generated/kubernetes-api/{{page.version}}/#secret-v1-core).
+* See the `imagePullSecrets` field of [PodSpec](/docs/reference/generated/kubernetes-api/{{page.version}}/#podspec-v1-core).
 
 {% endcapture %}
 

docs/tasks/configure-pod-container/security-context.md

@@ -304,7 +304,7 @@ for definitions of the capability constants.
 To assign SELinux labels to a Container, include the `seLinuxOptions` field in
 the `securityContext` section of your Pod or Container manifest. The
 `seLinuxOptions` field is an
-[SELinuxOptions](/docs/api-reference/{{page.version}}/#selinuxoptions-v1-core)
+[SELinuxOptions](/docs/reference/generated/kubernetes-api/{{page.version}}/#selinuxoptions-v1-core)
 object. Here's an example that applies an SELinux level:
 
 ```yaml
@@ -341,8 +341,8 @@ label given to all Containers in the Pod as well as the Volumes.
 
 {% capture whatsnext %}
 
-* [PodSecurityContext](/docs/api-reference/{{page.version}}/#podsecuritycontext-v1-core)
-* [SecurityContext](/docs/api-reference/{{page.version}}/#securitycontext-v1-core)
+* [PodSecurityContext](/docs/reference/generated/kubernetes-api/{{page.version}}/#podsecuritycontext-v1-core)
+* [SecurityContext](/docs/reference/generated/kubernetes-api/{{page.version}}/#securitycontext-v1-core)
 * [Tuning Docker with the newest security enhancements](https://opensource.com/business/15/3/docker-security-tuning)
 * [Security Contexts design document](https://git.k8s.io/community/contributors/design-proposals/auth/security_context.md)
 * [Ownership Management design document](https://git.k8s.io/community/contributors/design-proposals/storage/volume-ownership-management.md)