From 9812e6954dcc8d215c2999390abd17d79fa159f4 Mon Sep 17 00:00:00 2001 From: Stewart-YU Date: Fri, 17 Nov 2017 09:34:46 +0800 Subject: [PATCH] Update cluster-large.md delete addtion `/` in url link. --- docs/admin/cluster-large.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/admin/cluster-large.md b/docs/admin/cluster-large.md index fea0cb9d46..b443d42132 100644 --- a/docs/admin/cluster-large.md +++ b/docs/admin/cluster-large.md @@ -100,7 +100,7 @@ To avoid running into cluster addon resource issues, when creating a cluster wit * Scale memory and CPU limits for each of the following addons, if used, as you scale up the size of cluster (there is one replica of each handling the entire cluster so memory and CPU usage tends to grow proportionally with size/load on cluster): * [InfluxDB and Grafana](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/cluster-monitoring/influxdb/influxdb-grafana-controller.yaml) * [kubedns, dnsmasq, and sidecar](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/dns/kube-dns.yaml.in) - * [Kibana](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons//fluentd-elasticsearch/kibana-deployment.yaml) + * [Kibana](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/fluentd-elasticsearch/kibana-deployment.yaml) * Scale number of replicas for the following addons, if used, along with the size of cluster (there are multiple replicas of each so increasing replicas should help handle increased load, but, since load per replica also increases slightly, also consider increasing CPU/memory limits): * [elasticsearch](http://releases.k8s.io/{{page.githubbranch}}/cluster/addons/fluentd-elasticsearch/es-statefulset.yaml) * Increase memory and CPU limits slightly for each of the following addons, if used, along with the size of cluster (there is one replica per node but CPU/memory usage increases slightly along with cluster load/size as well):