Fix links to relocated kubelet TLS bootstrapping topic (#9332)

Fixes: #9330

content/en/docs/concepts/architecture/master-node-communication.md

@@ -38,8 +38,8 @@ Nodes should be provisioned with the public root certificate for the cluster
 such that they can connect securely to the apiserver along with valid client
 credentials. For example, on a default GCE deployment, the client credentials
 provided to the kubelet are in the form of a client certificate. See
-[kubelet TLS bootstrapping](/docs/admin/kubelet-tls-bootstrapping/) for
-automated provisioning of kubelet client certificates.
+[kubelet TLS bootstrapping](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/)
+for automated provisioning of kubelet client certificates.
 
 Pods that wish to connect to the apiserver can do so securely by leveraging a
 service account so that Kubernetes will automatically inject the public root

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

@@ -62,7 +62,7 @@ If you are using a guide involving Salt, see [Configuring Kubernetes with Salt](
 
 ### Securing the kubelet
   * [Master-Node communication](/docs/concepts/architecture/master-node-communication/)
-  * [TLS bootstrapping](/docs/admin/kubelet-tls-bootstrapping/)
+  * [TLS bootstrapping](/docs/reference/command-line-tools-reference/kubelet-tls-bootstrapping/)
   * [Kubelet authentication/authorization](/docs/admin/kubelet-authentication-authorization/)
 
 ## Optional Cluster Services