docs: address review feedback on DaemonSet overhead note

Soften the PriorityClass guidance, which is best-effort rather than a
guarantee, and add startup taints as the other option for keeping
workload pods off a node until DaemonSets are ready.

Also reflow the section to the one-sentence-per-line style used
throughout scheduling.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Signed-off-by: Vincent Creusot <vincent.creusot@gmail.com>

Author: vincentcreusot

website/content/en/docs/concepts/scheduling.md

@@ -133,17 +133,16 @@ Security groups for pods are [currently unsupported for Windows nodes](https://d
 
 ### DaemonSet overhead
 
-When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own
-requests, and picks an instance type large enough for the total.
+When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own requests, and picks an instance type large enough for the total.
 
-This overhead is only used to size the node. Karpenter does not reserve
-that capacity on the node after it joins the cluster, and it does not bind
-pods itself.
+This overhead is only used to size the node.
+Karpenter does not reserve that capacity on the node after it joins the cluster, and it does not bind pods itself.
 
 {{% alert title="Note" color="primary" %}}
-To guarantee DaemonSets get their capacity, give them a
-[PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/)
-higher than your workloads with `preemptionPolicy: PreemptLowerPriority`.
+Options to help DaemonSet pods get that capacity include:
+
+* [Startup taints]({{<ref "./nodepools/#spectemplatespecstartuptaints" >}}) will keep workload pods off the node until an external agent removes them, so DaemonSets that tolerate those taints will schedule first.
+* Setting a sufficiently high [PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/) on your DaemonSet pods will cause kube-scheduler to preempt lower-priority pods to make room for them. This is best-effort: pods of equal or higher priority will never be preempted, and PodDisruptionBudgets are only honored on a best-effort basis.
 {{% /alert %}}
 
 ## Selecting nodes

website/content/en/v1.0/concepts/scheduling.md

@@ -125,17 +125,16 @@ Security groups for pods are [currently unsupported for Windows nodes](https://d
 
 ### DaemonSet overhead
 
-When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own
-requests, and picks an instance type large enough for the total.
+When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own requests, and picks an instance type large enough for the total.
 
-This overhead is only used to size the node. Karpenter does not reserve
-that capacity on the node after it joins the cluster, and it does not bind
-pods itself.
+This overhead is only used to size the node.
+Karpenter does not reserve that capacity on the node after it joins the cluster, and it does not bind pods itself.
 
 {{% alert title="Note" color="primary" %}}
-To guarantee DaemonSets get their capacity, give them a
-[PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/)
-higher than your workloads with `preemptionPolicy: PreemptLowerPriority`.
+Options to help DaemonSet pods get that capacity include:
+
+* [Startup taints]({{<ref "./nodepools/#spectemplatespecstartuptaints" >}}) will keep workload pods off the node until an external agent removes them, so DaemonSets that tolerate those taints will schedule first.
+* Setting a sufficiently high [PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/) on your DaemonSet pods will cause kube-scheduler to preempt lower-priority pods to make room for them. This is best-effort: pods of equal or higher priority will never be preempted, and PodDisruptionBudgets are only honored on a best-effort basis.
 {{% /alert %}}
 
 ## Selecting nodes

website/content/en/v1.12/concepts/scheduling.md

@@ -133,17 +133,16 @@ Security groups for pods are [currently unsupported for Windows nodes](https://d
 
 ### DaemonSet overhead
 
-When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own
-requests, and picks an instance type large enough for the total.
+When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own requests, and picks an instance type large enough for the total.
 
-This overhead is only used to size the node. Karpenter does not reserve
-that capacity on the node after it joins the cluster, and it does not bind
-pods itself.
+This overhead is only used to size the node.
+Karpenter does not reserve that capacity on the node after it joins the cluster, and it does not bind pods itself.
 
 {{% alert title="Note" color="primary" %}}
-To guarantee DaemonSets get their capacity, give them a
-[PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/)
-higher than your workloads with `preemptionPolicy: PreemptLowerPriority`.
+Options to help DaemonSet pods get that capacity include:
+
+* [Startup taints]({{<ref "./nodepools/#spectemplatespecstartuptaints" >}}) will keep workload pods off the node until an external agent removes them, so DaemonSets that tolerate those taints will schedule first.
+* Setting a sufficiently high [PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/) on your DaemonSet pods will cause kube-scheduler to preempt lower-priority pods to make room for them. This is best-effort: pods of equal or higher priority will never be preempted, and PodDisruptionBudgets are only honored on a best-effort basis.
 {{% /alert %}}
 
 ## Selecting nodes

website/content/en/v1.13/concepts/scheduling.md

@@ -133,17 +133,16 @@ Security groups for pods are [currently unsupported for Windows nodes](https://d
 
 ### DaemonSet overhead
 
-When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own
-requests, and picks an instance type large enough for the total.
+When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own requests, and picks an instance type large enough for the total.
 
-This overhead is only used to size the node. Karpenter does not reserve
-that capacity on the node after it joins the cluster, and it does not bind
-pods itself.
+This overhead is only used to size the node.
+Karpenter does not reserve that capacity on the node after it joins the cluster, and it does not bind pods itself.
 
 {{% alert title="Note" color="primary" %}}
-To guarantee DaemonSets get their capacity, give them a
-[PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/)
-higher than your workloads with `preemptionPolicy: PreemptLowerPriority`.
+Options to help DaemonSet pods get that capacity include:
+
+* [Startup taints]({{<ref "./nodepools/#spectemplatespecstartuptaints" >}}) will keep workload pods off the node until an external agent removes them, so DaemonSets that tolerate those taints will schedule first.
+* Setting a sufficiently high [PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/) on your DaemonSet pods will cause kube-scheduler to preempt lower-priority pods to make room for them. This is best-effort: pods of equal or higher priority will never be preempted, and PodDisruptionBudgets are only honored on a best-effort basis.
 {{% /alert %}}
 
 ## Selecting nodes

website/content/en/v1.14/concepts/scheduling.md

@@ -133,17 +133,16 @@ Security groups for pods are [currently unsupported for Windows nodes](https://d
 
 ### DaemonSet overhead
 
-When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own
-requests, and picks an instance type large enough for the total.
+When Karpenter calculates the size of a node for a set of pending pods, it adds the resource requests of every DaemonSet that would run on that node to the pods' own requests, and picks an instance type large enough for the total.
 
-This overhead is only used to size the node. Karpenter does not reserve
-that capacity on the node after it joins the cluster, and it does not bind
-pods itself.
+This overhead is only used to size the node.
+Karpenter does not reserve that capacity on the node after it joins the cluster, and it does not bind pods itself.
 
 {{% alert title="Note" color="primary" %}}
-To guarantee DaemonSets get their capacity, give them a
-[PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/)
-higher than your workloads with `preemptionPolicy: PreemptLowerPriority`.
+Options to help DaemonSet pods get that capacity include:
+
+* [Startup taints]({{<ref "./nodepools/#spectemplatespecstartuptaints" >}}) will keep workload pods off the node until an external agent removes them, so DaemonSets that tolerate those taints will schedule first.
+* Setting a sufficiently high [PriorityClass](https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/) on your DaemonSet pods will cause kube-scheduler to preempt lower-priority pods to make room for them. This is best-effort: pods of equal or higher priority will never be preempted, and PodDisruptionBudgets are only honored on a best-effort basis.
 {{% /alert %}}
 
 ## Selecting nodes