From 13fd2d0f511d566c31fd4252d0471d03bbd5587a Mon Sep 17 00:00:00 2001 From: Xiaoyu Zhang Date: Fri, 24 Mar 2017 22:29:08 +0800 Subject: [PATCH] change the link icon The link now is a page of kubernetes.io, not a github's .md file any more. So I think use the link page's title( Building High-Availability Clusters) is fine. "high-availability.md" may be the older edition's link icon. --- docs/concepts/overview/components.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/concepts/overview/components.md b/docs/concepts/overview/components.md index 280b9b1f2c..7ac01baa20 100644 --- a/docs/concepts/overview/components.md +++ b/docs/concepts/overview/components.md @@ -18,7 +18,7 @@ unsatisfied). In theory, Master components can be run on any node in the cluster. However, for simplicity, current set up scripts typically start all master components on the same VM, and does not run user containers on this VM. See -[high-availability.md](/docs/admin/high-availability) for an example multi-master-VM setup. +[Building High-Availability Clusters](/docs/admin/high-availability) for an example multi-master-VM setup. Even in the future, when Kubernetes is fully self-hosting, it will probably be wise to only allow master components to schedule on a subset of nodes, to limit @@ -29,7 +29,7 @@ node-compromising security exploit. [kube-apiserver](/docs/admin/kube-apiserver) exposes the Kubernetes API; it is the front-end for the Kubernetes control plane. It is designed to scale horizontally (i.e., one scales -it by running more of them-- [high-availability.md](/docs/admin/high-availability)). +it by running more of them-- [Building High-Availability Clusters](/docs/admin/high-availability)). ### etcd