Show control plane link as glossary tooltips.

2020-08-05 13:02:41 +08:00
parent 8ea2145220
commit 97ffc14ac6
2 changed files with 2 additions and 2 deletions
@@ -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 {{< glossary_tooltip text="control plane" term_id="control-plane" >}}. 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

@@ -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). 
+{{< glossary_tooltip text="control plane" term_id="control-plane" >}}.

 ![Cluster Lifecycle Layers](/images/blog/2019-06-24-kubeadm-ha-v115/overview.png)