Skip to content

Commit d0a9477

Browse files
authored
Merge pull request #39442 from Amrita42/BZ1926013
BZ1926013: added an admonition for subscriptions
2 parents 8468eb3 + d09eb97 commit d0a9477

File tree

3 files changed

+14
-4
lines changed

3 files changed

+14
-4
lines changed

modules/installation-user-infra-generate-k8s-manifest-ignition.adoc

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -207,7 +207,12 @@ ifdef::baremetal,baremetal-restricted,ibm-z,ibm-power[]
207207
+
208208
[WARNING]
209209
====
210-
If you are installing a three-node cluster, skip the following step to allow the control plane nodes to be schedulable.
210+
If you are installing a three-node cluster, skip the following step to allow the control plane nodes to be schedulable. This is because control plane nodes then become worker nodes.
211+
====
212+
+
213+
[IMPORTANT]
214+
====
215+
When you configure control plane nodes from the default unschedulable to schedulable, additional subscriptions are required.
211216
====
212217
endif::baremetal,baremetal-restricted,ibm-z,ibm-power[]
213218

modules/nodes-nodes-working-marking.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@
66
= Understanding how to mark nodes as unschedulable or schedulable
77

88
By default, healthy nodes with a `Ready` status are
9-
marked as schedulable, meaning that new pods are allowed for placement on the
9+
marked as schedulable, which means that you can place new pods on the
1010
node. Manually marking a node as unschedulable blocks any new pods from being
1111
scheduled on the node. Existing pods on the node are not affected.
1212

modules/nodes-nodes-working-master-schedulable.adoc

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,18 +7,23 @@
77

88
You can configure control plane nodes to be
99
schedulable, meaning that new pods are allowed for placement on the master
10-
nodes. By default, control plane nodes are not schedulable.
10+
nodes. By default, control plane nodes are not schedulable.
1111

1212
You can set the masters to be schedulable, but must retain the worker nodes.
1313

1414
[NOTE]
1515
====
16-
You can deploy {product-title} with no worker nodes on a bare metal cluster.
16+
You can deploy {product-title} with no worker nodes on a bare metal cluster.
1717
In this case, the control plane nodes are marked schedulable by default.
1818
====
1919

2020
You can allow or disallow control plane nodes to be schedulable by configuring the `mastersSchedulable` field.
2121

22+
[IMPORTANT]
23+
====
24+
When you configure control plane nodes from the default unschedulable to schedulable, additional subscriptions are required. This is because control plane nodes then become worker nodes.
25+
====
26+
2227
.Procedure
2328

2429
. Edit the `schedulers.config.openshift.io` resource.

0 commit comments

Comments
 (0)