File tree Expand file tree Collapse file tree 1 file changed +6
-2
lines changed
content/en/docs/setup/best-practices Expand file tree Collapse file tree 1 file changed +6
-2
lines changed Original file line number Diff line number Diff line change @@ -24,7 +24,7 @@ on how your cluster is deployed.
24
24
25
25
To avoid running into cloud provider quota issues, when creating a cluster with many nodes,
26
26
consider:
27
- * Request a quota increase for cloud resources such as:
27
+ * Requesting a quota increase for cloud resources such as:
28
28
* Computer instances
29
29
* CPUs
30
30
* Storage volumes
@@ -33,7 +33,7 @@ consider:
33
33
* Number of load balancers
34
34
* Network subnets
35
35
* Log streams
36
- * Gate the cluster scaling actions to brings up new nodes in batches, with a pause
36
+ * Gating the cluster scaling actions to bring up new nodes in batches, with a pause
37
37
between batches, because some cloud providers rate limit the creation of new instances.
38
38
39
39
## Control plane components
@@ -66,6 +66,10 @@ When creating a cluster, you can (using custom tooling):
66
66
* start and configure additional etcd instance
67
67
* configure the {{< glossary_tooltip term_id="kube-apiserver" text="API server" >}} to use it for storing events
68
68
69
+ See [ Operating etcd clusters for Kubernetes] ( https://kubernetes.io/docs/tasks/administer-cluster/configure-upgrade-etcd/ ) and
70
+ [ Set up a High Availability etcd cluster with kubeadm] ( docs/setup/production-environment/tools/kubeadm/setup-ha-etcd-with-kubeadm/ )
71
+ for details on configuring and managing etcd for a large cluster.
72
+
69
73
## Addon resources
70
74
71
75
Kubernetes [ resource limits] ( /docs/concepts/configuration/manage-resources-containers/ )
You can’t perform that action at this time.
0 commit comments