Namespaces
Learn how we can create virtual clusters using Namespaces.
We'll cover the following
Introduction to Namespaces
The first thing to know is that Kubernetes Namespaces are not the same as kernel namespaces.
Kernel namespaces partition operating systems into virtual operating systems called containers
Kubernetes Namespaces partition Kubernetes clusters into virtual clusters called Namespaces
Note: We’ll capitalize Namespace when referring to Kubernetes Namespaces. This follows the pattern of capitalizing Kubernetes API objects and clarifies that we’re referring to Kubernetes Namespaces, not kernel namespaces.
It’s also important to know that Namespaces are a form of soft isolation and enable soft multi-tenancy. For example, we can create Namespaces for our dev, test, and qa environments and apply different quotas and policies to each. However, they won’t stop a compromised workload in one Namespace from impacting workloads in other Namespaces.
Playground
Use the following terminal to execute the commands for this lesson.
Get hands-on with 1400+ tech skills courses.