Skip to content

Commit 5220cdf

Browse files
rszszTim Bannister
andauthored
Explain leases in kube-node-lease namespace doc
Add a reference to `Lease` resource api doc Co-authored-by: Tim Bannister <[email protected]>
1 parent 497a523 commit 5220cdf

File tree

1 file changed

+4
-1
lines changed
  • content/en/docs/concepts/overview/working-with-objects

1 file changed

+4
-1
lines changed

content/en/docs/concepts/overview/working-with-objects/namespaces.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,10 @@ Kubernetes starts with four initial namespaces:
6262
* `default` The default namespace for objects with no other namespace
6363
* `kube-system` The namespace for objects created by the Kubernetes system
6464
* `kube-public` This namespace is created automatically and is readable by all users (including those not authenticated). This namespace is mostly reserved for cluster usage, in case that some resources should be visible and readable publicly throughout the whole cluster. The public aspect of this namespace is only a convention, not a requirement.
65-
* `kube-node-lease` The namespace for lease objects associated with each node, which improves the performance of [heartbeats](/docs/concepts/architecture/nodes/#heartbeats) as the cluster scales.
65+
* `kube-node-lease` This namespace holds [Lease](/docs/reference/kubernetes-api/cluster-resources/lease-v1/)
66+
objects associated with each node. Node leases allow the kubelet to send
67+
[heartbeats](/docs/concepts/architecture/nodes/#heartbeats) so that the control plane
68+
can detect node failure.
6669

6770
### Setting the namespace for a request
6871

0 commit comments

Comments
 (0)