Skip to content

Commit 53da9df

Browse files
Update affinity.md
1 parent 49e1c4b commit 53da9df

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed
Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,22 @@
11
---
2-
title: affinity
2+
title: Affinity
33
id: affinity
44
date: 2019-01-11
5-
full_link: /docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/
5+
full_link: /docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
66
short_description: >
7-
Node affinity is a set of rules used by the scheduler to determine where a pod can be placed.
7+
Rules used by the scheduler to determine where to place pods
88
aka:
99
tags:
10-
- core object
1110
- fundamental
1211
---
13-
Node affinity is a set of rules used by the scheduler to determine where a pod can be placed.
12+
13+
In Kubernetes, _affinity_ is a set of rules that give hints to the scheduler about where to place pods.
1414

1515
<!--more-->
16+
There are two kinds of affinity:
17+
* [node affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity)
18+
* [pod-to-pod affinity](/docs/concepts/scheduling-eviction/assign-pod-node/#inter-pod-affinity-and-anti-affinity)
1619

17-
The rules are defined using the familiar concepts of custom labels on {{< glossary_tooltip term_id="node" text="nodes">}}
20+
The rules are defined using the Kubernetes {{< glossary_tooltip term_id="label" text="labels">}},
1821
and {{< glossary_tooltip term_id="selector" text="selectors">}} specified in {{< glossary_tooltip term_id="pod" text="pods" >}},
1922
and they can be either required or preferred, depending on how strictly you want the scheduler to enforce them.

0 commit comments

Comments
 (0)