Kubernetes Namespace Concepts: Difference between revisions
Jump to navigation
Jump to search
| Line 16: | Line 16: | ||
A namespace is NOT a strong security boundary. | A namespace is NOT a strong security boundary. | ||
=The Default Namespace= | |||
It's not good practice to use the default namespace for anything of significance. | |||
=Namespace Operations= | =Namespace Operations= | ||
{{Internal|Kubernetes_Operations#Namespace_Operations|Namespace Operations}} | {{Internal|Kubernetes_Operations#Namespace_Operations|Namespace Operations}} | ||
Revision as of 20:51, 30 August 2019
External
Internal
Overview
A namespace is a construct that allows logically dividing a Kubernetes cluster for management purposes. A namespace provides scope for:
- named resources to avoid naming collisions
- delegating management authority to trusted users
- the ability to limit community resource consumption
In OpenShift, namespaces are known as OpenShift Projects.
A namespace is NOT a strong security boundary.
The Default Namespace
It's not good practice to use the default namespace for anything of significance.