From ffa299640288c24b37891edacada5b084d5249df Mon Sep 17 00:00:00 2001
From: Rajesh Deshpande <47311048+rajeshdeshpande02@users.noreply.github.com>
Date: Wed, 10 Apr 2019 07:28:12 +0530
Subject: [PATCH] Details about multiple namespaces (#13539)

k8s does not support nested namespaces but this is not specified anywhere in the document. I find this is the right place to document it as we introduce namespace concept here.  Also these details are important to mention specifically for users who are coming from Docker UCP background.
---
 .../docs/concepts/overview/working-with-objects/namespaces.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/content/en/docs/concepts/overview/working-with-objects/namespaces.md b/content/en/docs/concepts/overview/working-with-objects/namespaces.md
index 42cdf9d5ee..3e2f1a6206 100644
--- a/content/en/docs/concepts/overview/working-with-objects/namespaces.md
+++ b/content/en/docs/concepts/overview/working-with-objects/namespaces.md
@@ -25,7 +25,9 @@ teams, or projects.  For clusters with a few to tens of users, you should not
 need to create or think about namespaces at all.  Start using namespaces when you
 need the features they provide.
 
-Namespaces provide a scope for names.  Names of resources need to be unique within a namespace, but not across namespaces.
+Namespaces provide a scope for names.  Names of resources need to be unique within a namespace,
+but not across namespaces. Namespaces can not be nested inside one another and each Kubernetes 
+resources can only be in one namespace.
 
 Namespaces are a way to divide cluster resources between multiple users (via [resource quota](/docs/concepts/policy/resource-quotas/)).