From daa188613438c71c910b4c74453c443f4e68339e Mon Sep 17 00:00:00 2001 From: devasat Date: Tue, 9 Jul 2019 07:12:03 -0400 Subject: [PATCH] configure-upgrade-etcd.md: rename section header (#15328) The section heading refers to starting API Server, but the content is about starting etcd cluster. --- .../docs/tasks/administer-cluster/configure-upgrade-etcd.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md b/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md index 3b8e82a08a..68fc7c2fc3 100644 --- a/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md +++ b/content/en/docs/tasks/administer-cluster/configure-upgrade-etcd.md @@ -39,9 +39,9 @@ content_template: templates/task Operating etcd with limited resources is suitable only for testing purposes. For deploying in production, advanced hardware configuration is required. Before deploying etcd in production, see [resource requirement reference documentation](https://github.com/coreos/etcd/blob/master/Documentation/op-guide/hardware.md#example-hardware-configurations). -## Starting Kubernetes API server +## Starting etcd clusters -This section covers starting a Kubernetes API server with an etcd cluster in the deployment. +This section covers starting a single-node and multi-node etcd cluster. ### Single-node etcd cluster