You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/nw-nodeport-service-range-edit.adoc
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,11 +6,11 @@
6
6
[id="nw-nodeport-service-range-edit_{context}"]
7
7
= Expanding the node port range
8
8
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.
10
10
11
11
[IMPORTANT]
12
12
====
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.
14
14
====
15
15
16
16
.Prerequisites
@@ -21,17 +21,22 @@ Before you expand a node port range, consider that Red{nbsp}Hat has not performe
21
21
22
22
.Procedure
23
23
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:
0 commit comments