From 871534cd4e34d1bae096be5a80b516023478dd5f Mon Sep 17 00:00:00 2001 From: Ray Date: Sat, 8 Aug 2020 20:42:35 +0800 Subject: [PATCH] Update 2018-12-04-kubeadm-ga-release.md Links on blog pages should link to a page, not showing as a tooltip. --- content/en/blog/_posts/2018-12-04-kubeadm-ga-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2018-12-04-kubeadm-ga-release.md b/content/en/blog/_posts/2018-12-04-kubeadm-ga-release.md index f08ca6da69..8601a7b94d 100644 --- a/content/en/blog/_posts/2018-12-04-kubeadm-ga-release.md +++ b/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 {{< 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. +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