Skip to content

Commit f866f89

Browse files
authored
Update cnf-best-practices-expectations-permissions.adoc
1 parent 40e6675 commit f866f89

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/cnf-best-practices-expectations-permissions.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -258,7 +258,7 @@ Do not use exec probes if a CNF is doing CPU pinning.
258258

259259
In OpenShift Container Platform pod affinity and pod anti-affinity allow you to constrain which nodes your pod are eligible to be scheduled based on the key/value labels on other pods. There are two types of affinity rules, required and preferred. Required rules must be met, whereas preferred rules are best effort.
260260

261-
These pod affinity/anti-affinity rules are set in the pod specification as `matchExpressions` to a `labelSelector`. said dbhttps://docs.openshift.com/container-platform/latest/nodes/scheduling/nodes-scheduler-pod-affinity.html[Placing pods relative to other pods using affinity and anti-affinity rules]more information. The following example `Pod` CR illustrates pod affinity:
261+
These pod affinity/anti-affinity rules are set in the pod specification as `matchExpressions` to a `labelSelector`. See link:https://docs.openshift.com/container-platform/latest/nodes/scheduling/nodes-scheduler-pod-affinity.html[Placing pods relative to other pods using affinity and anti-affinity rules] for more information. The following example `Pod` CR illustrates pod affinity:
262262

263263
[source,yaml]
264264
----

0 commit comments

Comments
 (0)