summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorXingcai Zhang <zhangxingcai@ghostcloud.cn>2017-10-21 22:02:20 +0800
committerXingcai Zhang <zhangxingcai@ghostcloud.cn>2017-10-21 22:02:20 +0800
commit5939e2abb179bfd4eede8558415fbe9cb6e93c06 (patch)
tree9e0b11ccde2e209e8d2f512cc4b8cf7a46b38d2b
parent3b41c15de84ede5c002764f49f07e186345e96ba (diff)
update kube
-rw-r--r--contributors/design-proposals/scalability/kubemark.md4
-rw-r--r--contributors/design-proposals/scalability/scalability-testing.md2
2 files changed, 3 insertions, 3 deletions
diff --git a/contributors/design-proposals/scalability/kubemark.md b/contributors/design-proposals/scalability/kubemark.md
index 95888c94..e5f4b26b 100644
--- a/contributors/design-proposals/scalability/kubemark.md
+++ b/contributors/design-proposals/scalability/kubemark.md
@@ -45,8 +45,8 @@ components on non-default ports, and in the same time will allow to run multiple
generate credentials for cluster communication and pass them to HollowKubelet/HollowProxy to use. Master will treat all HollowNodes as
normal ones.
-![Kubmark architecture diagram for option 1](Kubemark_architecture.png?raw=true "Kubemark architecture overview")
-*Kubmark architecture diagram for option 1*
+![Kubemark architecture diagram for option 1](Kubemark_architecture.png?raw=true "Kubemark architecture overview")
+*Kubemark architecture diagram for option 1*
### Option 2
diff --git a/contributors/design-proposals/scalability/scalability-testing.md b/contributors/design-proposals/scalability/scalability-testing.md
index d0fcd1be..ae3e3534 100644
--- a/contributors/design-proposals/scalability/scalability-testing.md
+++ b/contributors/design-proposals/scalability/scalability-testing.md
@@ -19,7 +19,7 @@ Once we have a better understanding of their consequences, we may want to
decide to drop one of them, but we are not yet in that position.
-## Proposal 1 - Kubmark
+## Proposal 1 - Kubemark
In this proposal we are focusing on scalability testing of master components.
We do NOT focus on node-scalability - this issue should be handled separately.