From dd88014f302266a593abbcf83b3ea13ca7439680 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Sat, 10 Oct 2020 19:15:14 +0100 Subject: [PATCH] Remove statement about future of namespaces --- .../docs/concepts/overview/working-with-objects/namespaces.md | 3 --- 1 file changed, 3 deletions(-) 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 004c18ad2c..f078cb8636 100644 --- a/content/en/docs/concepts/overview/working-with-objects/namespaces.md +++ b/content/en/docs/concepts/overview/working-with-objects/namespaces.md @@ -28,9 +28,6 @@ resource 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/)). -In future versions of Kubernetes, objects in the same namespace will have the same -access control policies by default. - It is not necessary to use multiple namespaces just to separate slightly different resources, such as different versions of the same software: use [labels](/docs/concepts/overview/working-with-objects/labels) to distinguish