Skip to content

Commit 5a5c96b

Browse files
Add tooltip for affinity
1 parent 11afd15 commit 5a5c96b

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

content/en/docs/concepts/scheduling-eviction/pod-priority-preemption.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -252,12 +252,12 @@ Even so, the answer to the preceding question must be yes. If the answer is no,
252252
the Node is not considered for preemption.
253253
{{< /note >}}
254254

255-
If a pending Pod has inter-pod affinity to one or more of the lower-priority
256-
Pods on the Node, the inter-Pod affinity rule cannot be satisfied in the absence
257-
of those lower-priority Pods. In this case, the scheduler does not preempt any
258-
Pods on the Node. Instead, it looks for another Node. The scheduler might find a
259-
suitable Node or it might not. There is no guarantee that the pending Pod can be
260-
scheduled.
255+
If a pending Pod has inter-pod {{< glossary_tooltip text="affinity" term_id="affinity" >}}
256+
to one or more of the lower-priority Pods on the Node, the inter-Pod affinity
257+
rule cannot be satisfied in the absence of those lower-priority Pods. In this case,
258+
the scheduler does not preempt any Pods on the Node. Instead, it looks for another
259+
Node. The scheduler might find a suitable Node or it might not. There is no
260+
guarantee that the pending Pod can be scheduled.
261261

262262
Our recommended solution for this problem is to create inter-Pod affinity only
263263
towards equal or higher priority Pods.

0 commit comments

Comments
 (0)