From d99896ffbc12dd857a57cab104f801cd22dc52fd Mon Sep 17 00:00:00 2001 From: zhangxiaoyu-zidif Date: Mon, 30 Oct 2017 11:49:27 +0800 Subject: [PATCH] fix review --- docs/concepts/overview/working-with-objects/namespaces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/concepts/overview/working-with-objects/namespaces.md b/docs/concepts/overview/working-with-objects/namespaces.md index 17d92d0e8a..51b53439ac 100644 --- a/docs/concepts/overview/working-with-objects/namespaces.md +++ b/docs/concepts/overview/working-with-objects/namespaces.md @@ -48,7 +48,7 @@ Kubernetes starts with three initial namespaces: * `default` The default namespace for objects with no other namespace * `kube-system` The namespace for objects created by the Kubernetes system - * `kube-public` The namespace is created automatically and readable by all users (including those not authenticated). + * `kube-public` The namespace is created automatically and readable by all users (including those not authenticated). This namespace is mostly reserved for cluster usage, in case that some resources should be visible and readable publicly thoughout all the whole cluster. The public aspect of this namespace is only a convention, not a requirement. ### Setting the namespace for a request