If a resource is 'Namespaced' in Kubernetes, what does this mean?

If a resource is 'Namespaced' in Kubernetes, what does this mean?

• A. It exists globally across all namespaces
• B. It is tied to a particular Namespace and exists within the context of that Namespace
• C. It does not require a Namespace
• D. It is deprecated

Answer: (B)

Namespaced resources are scoped to a specific Namespace. This means the resource exists only within that Namespace and shares its boundary with other resources in the same Namespace, including access control and quotas. You must specify a Namespace when creating or interacting with it, and its name is unique inside that Namespace (you can have the same resource name in different Namespaces). If a resource is Namespaced, it cannot exist globally across all Namespaces. Cluster-wide (non-Namespaced) resources, by contrast, apply cluster scope and don’t belong to any single Namespace. So the correct understanding is that the resource is tied to a particular Namespace and exists within the context of that Namespace.

Namespaced resources are scoped to a specific Namespace. This means the resource exists only within that Namespace and shares its boundary with other resources in the same Namespace, including access control and quotas. You must specify a Namespace when creating or interacting with it, and its name is unique inside that Namespace (you can have the same resource name in different Namespaces). If a resource is Namespaced, it cannot exist globally across all Namespaces. Cluster-wide (non-Namespaced) resources, by contrast, apply cluster scope and don’t belong to any single Namespace. So the correct understanding is that the resource is tied to a particular Namespace and exists within the context of that Namespace.