From 497a5231df96b9108052f66fc6ff782264e655fc Mon Sep 17 00:00:00 2001 From: naisu <15970@pm.me> Date: Wed, 25 Aug 2021 17:20:22 +0200 Subject: [PATCH] Improve wording of `kube-node-lease` namespace doc Correct grammar and provide a reference to more detailed documentation of concepts mentioned. --- .../docs/concepts/overview/working-with-objects/namespaces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/overview/working-with-objects/namespaces.md b/content/en/docs/concepts/overview/working-with-objects/namespaces.md index 45f454516c..d921229e96 100644 --- a/content/en/docs/concepts/overview/working-with-objects/namespaces.md +++ b/content/en/docs/concepts/overview/working-with-objects/namespaces.md @@ -62,7 +62,7 @@ Kubernetes starts with four initial namespaces: * `default` The default namespace for objects with no other namespace * `kube-system` The namespace for objects created by the Kubernetes system * `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. - * `kube-node-lease` This namespace for the lease objects associated with each node which improves the performance of the node heartbeats as the cluster scales. + * `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. ### Setting the namespace for a request