Merge pull request #30088 from Shabirmean/patch-1

doc: update definition for namespaces
This commit is contained in:
Kubernetes Prow Robot
2021-10-15 03:24:54 -07:00
committed by GitHub
2 changed files with 3 additions and 4 deletions
@@ -10,8 +10,7 @@ weight: 30
<!-- overview --> <!-- overview -->
Kubernetes supports multiple virtual clusters backed by the same physical cluster. In Kubernetes, _namespaces_ provides a mechanism for isolating groups of resources within a single cluster. 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)_.
These virtual clusters are called namespaces.
<!-- body --> <!-- body -->
@@ -10,9 +10,9 @@ aka:
tags: tags:
- fundamental - fundamental
--- ---
An abstraction used by Kubernetes to support multiple virtual clusters on the same physical {{< glossary_tooltip text="cluster" term_id="cluster" >}}. An abstraction used by Kubernetes to support isolation of groups of resources within a single {{< glossary_tooltip text="cluster" term_id="cluster" >}}.
<!--more--> <!--more-->
Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. Names of resources need to be unique within a namespace, but not across namespaces. Namespaces are used to organize objects in a cluster and provide a way to divide cluster resources. 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)_.