Merge pull request #22968 from blueabysm/fix-links-which-pointed-to-unavailable-location

Fix links which pointed to unavailable location

content/en/blog/_posts/2018-12-04-kubeadm-ga-release.md

@@ -23,7 +23,7 @@ To keep kubeadm lean, focused, and vendor/infrastructure agnostic, the following
 - Non-critical add-ons, e.g. for monitoring, logging, and visualization
 - Specific cloud provider integrations
 
-Infrastructure provisioning, for example, is left to other SIG Cluster Lifecycle projects, such as the [Cluster API](https://github.com/kubernetes-sigs/cluster-api). Instead, kubeadm covers only the common denominator in every Kubernetes cluster: the [control plane](/docs/concepts/#kubernetes-control-plane). The user may install their preferred networking solution and other add-ons on top of Kubernetes *after* cluster creation.
+Infrastructure provisioning, for example, is left to other SIG Cluster Lifecycle projects, such as the [Cluster API](https://github.com/kubernetes-sigs/cluster-api). Instead, kubeadm covers only the common denominator in every Kubernetes cluster: the [control plane](/docs/concepts/overview/components/#control-plane-components). The user may install their preferred networking solution and other add-ons on top of Kubernetes *after* cluster creation.
 
 ### What kubeadm's GA release means
 

content/en/blog/_posts/2019-06-24-kubeadm-ha-v115.md

@@ -43,7 +43,7 @@ Those tasks are addressed by other SIG Cluster Lifecycle projects, such as the
 [Cluster API](https://github.com/kubernetes-sigs/cluster-api) for infrastructure provisioning and management. 
 
 Instead, kubeadm covers only the common denominator in every Kubernetes cluster: the
-[control plane](https://kubernetes.io/docs/concepts/#kubernetes-control-plane). 
+[control plane](/docs/concepts/overview/components/#control-plane-components).
 
 ![Cluster Lifecycle Layers](/images/blog/2019-06-24-kubeadm-ha-v115/overview.png)