Skip to content

Commit 9732805

Browse files
authored

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

content/en/docs/tasks/administer-cluster/namespaces.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -28,20 +28,22 @@ List the current namespaces in a cluster using:
2828
kubectl get namespaces
2929
```
3030
```console
31-
NAME STATUS AGE
32-
default Active 11d
33-
kube-system Active 11d
34-
kube-public Active 11d
31+
NAME STATUS AGE
32+
default Active 11d
33+
kube-node-lease Active 11d
34+
kube-public Active 11d
35+
kube-system Active 11d
3536
```
3637

37-
Kubernetes starts with three initial namespaces:
38+
Kubernetes starts with four initial namespaces:
3839

3940
* `default` The default namespace for objects with no other namespace
40-
* `kube-system` The namespace for objects created by the Kubernetes system
41+
* `kube-node-lease` This namespace holds [Lease](/docs/concepts/architecture/leases/) objects associated with each node. Node leases allow the kubelet to send [heartbeats](/docs/concepts/architecture/nodes/#heartbeats) so that the control plane can detect node failure.
4142
* `kube-public` This namespace is created automatically and is readable by all users
4243
(including those not authenticated). This namespace is mostly reserved for cluster usage,
4344
in case that some resources should be visible and readable publicly throughout the whole cluster.
4445
The public aspect of this namespace is only a convention, not a requirement.
46+
* `kube-system` The namespace for objects created by the Kubernetes system
4547

4648
You can also get the summary of a specific namespace using:
4749

0 commit comments

Comments
 (0)