From 7dcfaf0b87be75b8c9c138df475e15d662fbdce6 Mon Sep 17 00:00:00 2001 From: jianglingxia Date: Mon, 27 Feb 2017 16:33:50 +0800 Subject: [PATCH] cluster-components-could be running could be doing sth --- 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 a3d4f37779..1f3404d6e4 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 run on any node in the cluster. However, +Master components could in theory be running 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.