Namespaces are intended for use in environments with many users spread across multiple teams or projects.
They provide a framework for names. Resource names must be unique within a namespace, but not across namespaces. Namespaces cannot be nested within each other and each Kubernetes resource can only be in one namespace. Further, they are a way to share cluster resources between multiple users (via resource quotas).
It is not necessary to use multiple namespaces just to separate slightly different resources, such as different versions of the same software. Here it is recommended to work with labels to distinguish resources within the same namespace.
Included in the following risks
Any Questions?
Please feel free to contact us for any question that is not answered yet.
We are looking forward to get in contact with you!
