Skip to content

Commit 6c0827a

Browse files
committed
OSDOCS-8659: Apply CQA updates
- https://issues.redhat.com/browse/OSDOCS-8659
1 parent 649c738 commit 6c0827a

File tree

1 file changed

+11
-6
lines changed

1 file changed

+11
-6
lines changed

modules/nw-nodeport-service-range-edit.adoc

Lines changed: 11 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,11 @@
66
[id="nw-nodeport-service-range-edit_{context}"]
77
= Expanding the node port range
88

9-
You can expand the node port range for your cluster. However, after you install your {product-title} cluster, you cannot contract the node port range on either side.
9+
You can only expand the node port range for your cluster. After you install your {product-title} cluster, you cannot shrink the node port range on either side of the currently configured range.
1010

1111
[IMPORTANT]
1212
====
13-
Before you expand a node port range, consider that Red{nbsp}Hat has not performed testing outside the default port range of `30000-32768`. For ranges outside the default port range, ensure that you test to verify the expanding node port range does not impact your cluster. If you expanded the range and a port allocation issue occurs, create a new cluster and set the required range for it.
13+
Red{nbsp}Hat has not performed testing outside the default port range of `30000-32768`. For ranges outside the default port range, ensure that you test to verify that expanding your node port range does not impact your cluster. If you expanded the range and a port allocation issue occurs, create a new cluster and set the required range for it.
1414
====
1515

1616
.Prerequisites
@@ -21,17 +21,22 @@ Before you expand a node port range, consider that Red{nbsp}Hat has not performe
2121
2222
.Procedure
2323

24-
* Expand the range for the `serviceNodePortRange` parameter in the `network.config.openshift.io` object that your cluster uses to manage traffic for pods by entering the following command in your command-line interface (CLI):
24+
* To expand the range for the `serviceNodePortRange` parameter in the `network.config.openshift.io` object that your cluster uses to manage traffic for pods, enter the following command:
2525
+
2626
[source,terminal]
2727
----
2828
$ oc patch network.config.openshift.io cluster --type=merge -p \
2929
'{
3030
"spec":
31-
{ "serviceNodePortRange": "<port_range>" } <1>
31+
{ "serviceNodePortRange": "<port_range>" }
3232
}'
3333
----
34-
<1> Where `<port_range>` is your expanded range, such as `30000-32900`.
34+
+
35+
---
36+
where:
37+
38+
`<port_range>`:: specifies your expanded range, such as `30000-32900`.
39+
---
3540
+
3641
[TIP]
3742
====
@@ -57,7 +62,7 @@ network.config.openshift.io/cluster patched
5762

5863
.Verification
5964

60-
* To confirm a successful configuration, enter the following command. The update can take several minutes to apply.
65+
* To confirm that the updated configuration is active, enter the following command. The update can take several minutes to apply.
6166
+
6267
[source,terminal]
6368
----

0 commit comments

Comments
 (0)