kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Add tooltip for affinity

This commit is contained in:
Meha Bhalodiya 2021-06-16 11:11:15 +05:30 committed by GitHub
parent 11afd156d2
commit 5a5c96b2cc
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -252,12 +252,12 @@ Even so, the answer to the preceding question must be yes. If the answer is no,
the Node is not considered for preemption. the Node is not considered for preemption.
{{< /note >}} {{< /note >}}
If a pending Pod has inter-pod affinity to one or more of the lower-priority If a pending Pod has inter-pod {{< glossary_tooltip text="affinity" term_id="affinity" >}}
Pods on the Node, the inter-Pod affinity rule cannot be satisfied in the absence to one or more of the lower-priority Pods on the Node, the inter-Pod affinity
of those lower-priority Pods. In this case, the scheduler does not preempt any rule cannot be satisfied in the absence of those lower-priority Pods. In this case,
Pods on the Node. Instead, it looks for another Node. The scheduler might find a the scheduler does not preempt any Pods on the Node. Instead, it looks for another
suitable Node or it might not. There is no guarantee that the pending Pod can be Node. The scheduler might find a suitable Node or it might not. There is no
scheduled. guarantee that the pending Pod can be scheduled.
Our recommended solution for this problem is to create inter-Pod affinity only Our recommended solution for this problem is to create inter-Pod affinity only
towards equal or higher priority Pods. towards equal or higher priority Pods.