You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/tasks/administer-cluster/namespaces.md
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,20 +28,22 @@ List the current namespaces in a cluster using:
28
28
kubectl get namespaces
29
29
```
30
30
```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
35
36
```
36
37
37
-
Kubernetes starts with three initial namespaces:
38
+
Kubernetes starts with four initial namespaces:
38
39
39
40
*`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.
41
42
*`kube-public` This namespace is created automatically and is readable by all users
42
43
(including those not authenticated). This namespace is mostly reserved for cluster usage,
43
44
in case that some resources should be visible and readable publicly throughout the whole cluster.
44
45
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
45
47
46
48
You can also get the summary of a specific namespace using:
0 commit comments