Skip to content

Commit 87b43ec

Browse files
author
Michael Burke
committed
Fixed problematic ifeval
1 parent 77fae7c commit 87b43ec

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

modules/olm-overriding-operator-pod-affinity.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,15 @@ ifeval::["{context}" == "nodes-scheduler-node-affinity"]
1111
:node:
1212
endif::[]
1313
ifeval::["{context}" == "olm-adding-operators-to-a-cluster"]
14-
:olm:
14+
:oplm:
1515
endif::[]
1616

1717
:_mod-docs-content-type: PROCEDURE
1818
[id="olm-overriding-operator-pod-affinity_{context}"]
1919

20-
ifdef::olm[]
20+
ifdef::oplm[]
2121
= Controlling where an Operator is installed
22-
endif::olm[]
22+
endif::oplm[]
2323

2424
ifdef::pod[]
2525
= Using pod affinity and anti-affinity to control where an Operator is installed
@@ -40,9 +40,9 @@ endif::openshift-dedicated,openshift-rosa[]
4040
* If you want Operators that work together scheduled on the same host or on hosts located on the same rack
4141
* If you want Operators dispersed throughout the infrastructure to avoid downtime due to network or hardware issues
4242

43-
ifdef::olm[]
43+
ifdef::oplm[]
4444
You can control where an Operator pod is installed by adding node affinity, pod affinity, or pod anti-affinity constraints to the Operator's `Subscription` object. Node affinity is a set of rules used by the scheduler to determine where a pod can be placed. Pod affinity enables you to ensure that related pods are scheduled to the same node. Pod anti-affinity allows you to prevent a pod from being scheduled on a node.
45-
endif::olm[]
45+
endif::oplm[]
4646

4747
ifdef::pod[]
4848
You can control where an Operator pod is installed by adding a pod affinity or anti-affinity to the Operator's `Subscription` object.
@@ -52,9 +52,9 @@ ifdef::node[]
5252
You can control where an Operator pod is installed by adding a node affinity constraints to the Operator's `Subscription` object.
5353
endif::node[]
5454

55-
ifdef::olm[]
55+
ifdef::oplm[]
5656
The following examples show how to use node affinity or pod anti-affinity to install an instance of the Custom Metrics Autoscaler Operator to a specific node in the cluster:
57-
endif::olm[]
57+
endif::oplm[]
5858
ifdef::node[]
5959
The following examples show how to use node affinity to install an instance of the Custom Metrics Autoscaler Operator to a specific node in the cluster:
6060
endif::node[]
@@ -188,7 +188,7 @@ To control the placement of an Operator pod, complete the following steps:
188188
. Edit the Operator `Subscription` object to add an affinity:
189189
+
190190
ifndef::pod[]
191-
ifdef::olm[]
191+
ifdef::oplm[]
192192
[source,yaml]
193193
----
194194
apiVersion: operators.coreos.com/v1alpha1
@@ -213,7 +213,7 @@ spec:
213213
#...
214214
----
215215
<1> Add a `nodeAffinity`, `podAffinity`, or `podAntiAffinity`. See the Additional resources section that follows for information about creating the affinity.
216-
endif::olm[]
216+
endif::oplm[]
217217

218218
ifdef::node[]
219219
[source,yaml]

0 commit comments

Comments
 (0)