Kubernetes Namespaces

• ✓ A.Namespaces provide a way to divide cluster resources between multiple users or teams.
• B.All Kubernetes resources must be created within a namespace.
• C.Namespaces provide network isolation by default.
• ✓ D.Deleting a namespace will delete all resources in it.
• ✓ E.Resource quotas can be applied to a namespace to limit total resource consumption.

Why A: Option A is correct because namespaces partition cluster resources into virtual sub-clusters, enabling multi-tenancy and resource isolation for different teams or users. Option D is correct because when a namespace is deleted, Kubernetes automatically removes all resources (e.g., Pods, Services) that belong to that namespace. Option E is incorrect: while resource quotas can be applied to namespaces, they are an optional feature and not an inherent property; the statement is misleading because quotas must be explicitly configured and do not limit all resource types (e.g., node resources).

• ✓ A.Namespaces provide a way to divide cluster resources among multiple users
• B.Namespaces act as a strong security boundary by default
• ✓ C.Namespaces help organize objects in a cluster
• D.Every resource must be created in a namespace
• E.Resources in different namespaces cannot communicate with each other

Why A: Option A is correct because Namespaces in Kubernetes provide a mechanism for partitioning a single cluster into multiple virtual clusters, enabling resource quota management and access control for different users or teams. This allows administrators to divide cluster resources (like CPU, memory, and storage) among multiple users via ResourceQuotas and LimitRanges, without requiring separate physical clusters.

• ✓ A.Resource names must be unique within a namespace
• B.Namespaces provide network isolation by default
• C.All Kubernetes resources are namespaced
• ✓ D.Namespaces provide a way to divide cluster resources between multiple users
• E.You can delete a namespace without affecting the resources inside it

Why A: Option A is correct because Kubernetes enforces that resource names must be unique within a namespace. This is a fundamental constraint: within a given namespace, you cannot have two resources of the same type (e.g., two Pods) with the same name. This uniqueness allows the API server to resolve resource references unambiguously when using namespaced resources.

• A.Services in different namespaces cannot communicate with each other
• B.Every Kubernetes object must be created in a namespace
• ✓ C.Deleting a namespace will delete all objects in it
• ✓ D.Namespaces can be used to implement resource quotas
• E.Namespaces provide a way to divide cluster resources between multiple users

Why C: Option C is correct because deleting a namespace triggers cascading deletion of all objects within it. Option D is correct because resource quotas can be applied per namespace to limit aggregate resource consumption. Option E is not entirely accurate: namespaces provide logical isolation, but dividing cluster resources among multiple users requires additional mechanisms like RBAC and resource quotas. Without those, namespaces alone do not enforce resource division.