From 40bf97accf52ea183e3cae2264152d0bd64e7090 Mon Sep 17 00:00:00 2001 From: jianglingxia Date: Tue, 28 Feb 2017 09:50:01 +0800 Subject: [PATCH] update cluster-components.md In theory,Master components can be run.... --- docs/admin/cluster-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/cluster-components.md b/docs/admin/cluster-components.md index 1f3404d6e4..878cb443a2 100644 --- a/docs/admin/cluster-components.md +++ b/docs/admin/cluster-components.md @@ -15,7 +15,7 @@ cluster (e.g., scheduling), and detecting and responding to cluster events (e.g., starting up a new pod when a replication controller's 'replicas' field is unsatisfied). -Master components could in theory be running on any node in the cluster. However, +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.