From 961f82cf22beb2fc4cf282fbc828b990202afe48 Mon Sep 17 00:00:00 2001
From: Shauna Diaz <shdiaz@redhat.com>
Date: Tue, 13 Dec 2022 14:14:57 -0500
Subject: [PATCH] OSDOCS-4692: Extending the nodeport range

---
 .../microshift-using-config-tools.adoc        |  6 +-
 ...croshift-config-auto-apply-manifests.adoc} |  0
 .../microshift-config-nodeport-limits.adoc    | 63 +++++++++++++++++++
 3 files changed, 66 insertions(+), 3 deletions(-)
 rename modules/{microshift-auto-apply-manifests.adoc => microshift-config-auto-apply-manifests.adoc} (100%)
 create mode 100644 modules/microshift-config-nodeport-limits.adoc

diff --git a/microshift_configuring/microshift-using-config-tools.adoc b/microshift_configuring/microshift-using-config-tools.adoc
index 390291fd84..5491dbe8f5 100644
--- a/microshift_configuring/microshift-using-config-tools.adoc
+++ b/microshift_configuring/microshift-using-config-tools.adoc
@@ -5,10 +5,10 @@ include::_attributes/attributes-microshift.adoc[]
 :context: microshift-configuring
 toc::[]
 
-{product-title} uses a YAML configuration file to execute commands. 
+{product-title} uses a YAML configuration file to execute commands.
 
 //include::modules/microshift-config-cli-manifests.adoc[leveloffset=+1]
 
 include::modules/microshift-config-yaml.adoc[leveloffset=+1]
-
-include::modules/microshift-auto-apply-manifests.adoc[leveloffset=+1]
\ No newline at end of file
+include::modules/microshift-config-auto-apply-manifests.adoc[leveloffset=+1]
+include::modules/microshift-config-nodeport-limits.adoc[leveloffset=+1]
\ No newline at end of file
diff --git a/modules/microshift-auto-apply-manifests.adoc b/modules/microshift-config-auto-apply-manifests.adoc
similarity index 100%
rename from modules/microshift-auto-apply-manifests.adoc
rename to modules/microshift-config-auto-apply-manifests.adoc
diff --git a/modules/microshift-config-nodeport-limits.adoc b/modules/microshift-config-nodeport-limits.adoc
new file mode 100644
index 0000000000..c80a1f1366
--- /dev/null
+++ b/modules/microshift-config-nodeport-limits.adoc
@@ -0,0 +1,63 @@
+// Module included in the following assemblies:
+//
+// * microshift/using-config-tools.adoc
+
+:_content-type: CONCEPT
+[id="microshift-nodeport-range-limits_{context}"]
+= Extending the NodePort service range
+
+The `serviceNodePortRange` setting allows the extension of the port range available to NodePort services. This option is useful when specific standard ports under the `30000-32767` need to be exposed. For example, your device needs to expose the `1883/tcp` MQ Telemetry Transport (MQTT) port on the network because some client devices cannot use a different port.
+
+[IMPORTANT]
+NodePorts can overlap with system ports, causing a malfunction of the system or {product-title}.
+
+Considerations when configuring the NodePort service ranges:
+
+* Do not create any NodePort service without an explicit `nodePort` selection. In this case, the port is assigned randomly by the `kube-apiserver`.
+
+* Do not create any NodePort service for any system service port, {product-title} port, or other services you expose on your device `HostNetwork`.
+
+* Table one specifies ports to avoid when extending the port range:
+
+.Ports to avoid.
+[cols="2",options="header"]
+|===
+|Port
+|Description
+
+|22/tcp
+|SSH port
+
+|80/tcp
+|OpenShift Router HTTP endpoint
+
+|443/tcp
+|OpenShift Router HTTPS endpoint
+
+|1936/tcp
+|Metrics service for the openshift-router, not exposed today
+
+|2379/tcp
+|etcd port
+
+|2380/tcp
+|etcd port
+
+|6443
+|kubernetes API
+
+|8445/tcp
+|openshift-route-controller-manager
+
+|9537/tcp
+|cri-o metrics
+
+|10250/tcp
+|kubelet
+
+|10248/tcp
+|kubelet healthz port
+
+|10259/tcp
+|kube scheduler
+|===