# Kubernetes Namespace

> A named area in one Kubernetes cluster. It keeps teams and apps apart.

**Field:** Infrastructure  
**Category:** Container Orchestration  
**Also known as:** K8s Namespace, Namespace (Kubernetes), kube-system

## Think of it like

It is like rooms in one house. Each room can have its own lamp, with the same name.

## Definition

A Kubernetes namespace splits one cluster into named areas. Each name only has to be unique inside its own namespace. So two teams can both have an app called web. Rules and limits can be set per namespace. A new cluster starts with four, and your work goes in the one called default unless you say otherwise.

## Example

Jack's cluster has a shop-test and a shop-live namespace. Both hold an app called web, and a test run can only touch shop-test.

## Example code

```console
$ kubectl get namespace
NAME              STATUS   AGE
default           Active   1d
kube-node-lease   Active   1d
kube-public       Active   1d
kube-system       Active   1d
```

A new cluster starts with these four. Your own apps go in default until you make more.

## Why it matters

Namespaces let many teams share one cluster safely. Each can have its own rules and its own share of the machines.

## Common mistake

Thinking a namespace is a wall for security on its own. It only splits names; you still need access rules on top.

## Three principles

- **Names stay local.** Unique inside a namespace, not across them.
- **Rules per area.** Limits and access are set per namespace.
- **One level only.** A namespace cannot hold another one.

## Related terms

- [Kubernetes Cluster](https://learn.benibix.com/term/infrastructure/kubernetes-cluster)
- [kubectl](https://learn.benibix.com/term/infrastructure/kubectl)
- [Kubernetes (K8s)](https://learn.benibix.com/term/infrastructure/kubernetes)
- [Role-Based Access Control (RBAC)](https://learn.benibix.com/term/development/role-based-access-control)
- [Linux Namespace](https://learn.benibix.com/term/infrastructure/linux-namespace)

## Told apart from

- [Linux Namespace vs Kubernetes Namespace](https://learn.benibix.com/compare/linux-namespace-vs-kubernetes-namespace): People think a Kubernetes namespace is a Linux namespace, and it is not. A Linux namespace is a wall inside one computer. It hides the other programs from a container. A Kubernetes namespace is a label. It splits a cluster into groups, such as one per team. By itself, it walls nothing off.

![One cluster split into three dashed areas named default, shop-test and shop-live. Each area holds a pod called web. The same name is allowed because each one lives in a different namespace.](https://learn.benibix.com/diagrams/inf-k8s-namespaces.svg)

---

Source: https://learn.benibix.com/term/infrastructure/kubernetes-namespace
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-17
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
