Skip to content

Commit 0ca22ac

Browse files
committed
doc: update definition for namespaces
Update namespace definition to not use _Virtual Clusters_ as a means of explaining namespaces. Motif: KubeCon NA 21 Talk on ***"Beyond Namespaces: Virtual Clusters are the Future of Multi-Tenancy - Lukas Gentele, Loft Labs"***
1 parent d2f2b29 commit 0ca22ac

File tree

1 file changed

+1
-2
lines changed
  • content/en/docs/concepts/overview/working-with-objects

1 file changed

+1
-2
lines changed

content/en/docs/concepts/overview/working-with-objects/namespaces.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,8 +10,7 @@ weight: 30
1010

1111
<!-- overview -->
1212

13-
Kubernetes supports multiple virtual clusters backed by the same physical cluster.
14-
These virtual clusters are called namespaces.
13+
Namespaces in Kubernetes provides a mechanism for scoping cluster resources by name. Names of resources need to be unique within a namespace, but not across namespaces. Namespace based scoping is applicable only for namespaced objects _(e.g. Deployments, Services, etc)_ and not for cluster-wide objects _(e.g. StorageClass, Nodes, PersistentVolumes, etc)_.
1514

1615
<!-- body -->
1716

0 commit comments

Comments
 (0)