Remove redirect and point to the generated kubectl doc directly (#8208)

Since we now generate the kubectl doc for each release, it is no longer necessary to use the old redirects. Cleaning up the references throughout the documents.

docs/tutorials/stateful-application/basic-stateful-set.md

@@ -63,7 +63,7 @@ It creates a [Headless Service](/docs/concepts/services-networking/service/#head
 Download the example above, and save it to a file named `web.yaml`
 
 You will need to use two terminal windows. In the first terminal, use 
-[`kubectl get`](/docs/user-guide/kubectl/{{page.version}}/#get) to watch the creation 
+[`kubectl get`](/docs/reference/generated/kubectl/kubectl-commands/#get) to watch the creation 
 of the StatefulSet's Pods.
 
 ```shell
@@ -71,7 +71,7 @@ kubectl get pods -w -l app=nginx
 ```
 
 In the second terminal, use 
-[`kubectl create`](/docs/user-guide/kubectl/{{page.version}}/#create) to create the 
+[`kubectl create`](/docs/reference/generated/kubectl/kubectl-commands/#create) to create the 
 Headless Service and StatefulSet defined in `web.yaml`.
 
 ```shell
@@ -143,7 +143,7 @@ replicas, it creates two Pods, `web-0` and `web-1`.
 ### Using Stable Network Identities
 
 Each Pod has a stable hostname based on its ordinal index. Use
-[`kubectl exec`](/docs/user-guide/kubectl/{{page.version}}/#exec) to execute the 
+[`kubectl exec`](/docs/reference/generated/kubectl/kubectl-commands/#exec) to execute the 
 `hostname` command in each Pod. 
 
 ```shell
@@ -152,7 +152,7 @@ web-0
 web-1
 ```
 
-Use [`kubectl run`](/docs/user-guide/kubectl/{{page.version}}/#run) to execute 
+Use [`kubectl run`](/docs/reference/generated/kubectl/kubectl-commands/#run) to execute 
 a container that provides the `nslookup` command from the `dnsutils` package. 
 Using `nslookup` on the Pods' hostnames, you can examine their in-cluster DNS 
 addresses.
@@ -184,7 +184,7 @@ In one terminal, watch the StatefulSet's Pods.
 kubectl get pod -w -l app=nginx
 ```
 In a second terminal, use
-[`kubectl delete`](/docs/user-guide/kubectl/{{page.version}}/#delete) to delete all 
+[`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands/#delete) to delete all 
 the Pods in the StatefulSet.
 
 ```shell
@@ -336,8 +336,8 @@ mounted to the appropriate mount points.
 ## Scaling a StatefulSet
 Scaling a StatefulSet refers to increasing or decreasing the number of replicas. 
 This is accomplished by updating the `replicas` field. You can use either
-[`kubectl scale`](/docs/user-guide/kubectl/{{page.version}}/#scale) or
-[`kubectl patch`](/docs/user-guide/kubectl/{{page.version}}/#patch) to scale a StatefulSet.
+[`kubectl scale`](/docs/reference/generated/kubectl/kubectl-commands/#scale) or
+[`kubectl patch`](/docs/reference/generated/kubectl/kubectl-commands/#patch) to scale a StatefulSet.
 
 ### Scaling Up
 
@@ -727,7 +727,7 @@ In one terminal window, watch the Pods in the StatefulSet.
 kubectl get pods -w -l app=nginx
 ```
 
-Use [`kubectl delete`](/docs/user-guide/kubectl/{{page.version}}/#delete) to delete the 
+Use [`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands/#delete) to delete the 
 StatefulSet. Make sure to supply the `--cascade=false` parameter to the 
 command. This parameter tells Kubernetes to only delete the StatefulSet, and to 
 not delete any of its Pods.

docs/tutorials/stateful-application/zookeeper.md

@@ -77,7 +77,7 @@ and a [StatefulSet](/docs/concepts/workloads/controllers/statefulset/).
 {% include code.html language="yaml" file="zookeeper.yaml" ghlink="/docs/tutorials/stateful-application/zookeeper.yaml" %}
 
 Open a terminal, and use the
-[`kubectl apply`](/docs/user-guide/kubectl/{{page.version}}/#apply) command to create the
+[`kubectl apply`](/docs/reference/generated/kubectl/kubectl-commands/#apply) command to create the
 manifest.
 
 ```shell
@@ -94,7 +94,7 @@ poddisruptionbudget "zk-pdb" created
 statefulset "zk" created
 ```
 
-Use [`kubectl get`](/docs/user-guide/kubectl/{{page.version}}/#get) to watch the
+Use [`kubectl get`](/docs/reference/generated/kubectl/kubectl-commands/#get) to watch the
 StatefulSet controller create the StatefulSet's Pods.
 
 ```shell
@@ -129,7 +129,7 @@ a [ZooKeeper](http://www-us.apache.org/dist/zookeeper/stable/) server.
 
 Because there is no terminating algorithm for electing a leader in an anonymous network, Zab requires explicit membership configuration to perform leader election. Each server in the ensemble needs to have a unique identifier, all servers need to know the global set of identifiers, and each identifier needs to be associated with a network address.
 
-Use [`kubectl exec`](/docs/user-guide/kubectl/{{page.version}}/#exec) to get the hostnames
+Use [`kubectl exec`](/docs/reference/generated/kubectl/kubectl-commands/#exec) to get the hostnames
 of the Pods in the `zk` StatefulSet.
 
 ```shell
@@ -307,7 +307,7 @@ in memory state, to storage media. Using WALs to provide durability is a common
 technique for applications that use consensus protocols to achieve a replicated
 state machine.
 
-Use the [`kubectl delete`](/docs/user-guide/kubectl/{{page.version}}/#delete) command to delete the
+Use the [`kubectl delete`](/docs/reference/generated/kubectl/kubectl-commands/#delete) command to delete the
 `zk` StatefulSet.
 
 ```shell
@@ -514,7 +514,7 @@ log4j.appender.CONSOLE.layout.ConversionPattern=%d{ISO8601} [myid:%X{myid}] - %-
 
 This is the simplest possible way to safely log inside the container. Because the applications write logs to standard out, Kubernetes will handle log rotation for you. Kubernetes also implements a sane retention policy that ensures application logs written to standard out and standard error do not exhaust local storage media.
 
-Use [`kubectl logs`](/docs/user-guide/kubectl/{{page.version}}/#logs) to retrieve the last 20 log lines from one of the Pods.
+Use [`kubectl logs`](/docs/reference/generated/kubectl/kubectl-commands/#logs) to retrieve the last 20 log lines from one of the Pods.
 
 ```shell
 kubectl logs zk-0 --tail 20
@@ -872,7 +872,7 @@ Use this command to get the nodes in your cluster.
 kubectl get nodes
 ```
 
-Use [`kubectl cordon`](/docs/user-guide/kubectl/{{page.version}}/#cordon) to
+Use [`kubectl cordon`](/docs/reference/generated/kubectl/kubectl-commands/#cordon) to
 cordon all but four of the nodes in your cluster.
 
 ```shell
@@ -909,7 +909,7 @@ kubernetes-minion-group-ixsl
 kubernetes-minion-group-i4c4
 ```
 
-Use [`kubectl drain`](/docs/user-guide/kubectl/{{page.version}}/#drain) to cordon and
+Use [`kubectl drain`](/docs/reference/generated/kubectl/kubectl-commands/#drain) to cordon and
 drain the node on which the `zk-0` Pod is scheduled.
 
 ```shell
@@ -1020,7 +1020,7 @@ dataLength = 5
 numChildren = 0
 ```
 
-Use [`kubectl uncordon`](/docs/user-guide/kubectl/{{page.version}}/#uncordon) to uncordon the first node.
+Use [`kubectl uncordon`](/docs/reference/generated/kubectl/kubectl-commands/#uncordon) to uncordon the first node.
 
 ```shell
 kubectl uncordon kubernetes-minion-group-pb41