Skip to content

Commit adb5002

Browse files
authored
Merge pull request #53781 from ShaunaDiaz/OSDOCS-4692
OSDOCS-4692: Extending the nodeport range
2 parents 335ac90 + e83b8d9 commit adb5002

File tree

3 files changed

+66
-3
lines changed

3 files changed

+66
-3
lines changed

microshift_configuring/microshift-using-config-tools.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,10 +5,10 @@ include::_attributes/attributes-microshift.adoc[]
55
:context: microshift-configuring
66
toc::[]
77

8-
{product-title} uses a YAML configuration file to execute commands.
8+
{product-title} uses a YAML configuration file to execute commands.
99

1010
//include::modules/microshift-config-cli-manifests.adoc[leveloffset=+1]
1111

1212
include::modules/microshift-config-yaml.adoc[leveloffset=+1]
13-
14-
include::modules/microshift-auto-apply-manifests.adoc[leveloffset=+1]
13+
include::modules/microshift-config-auto-apply-manifests.adoc[leveloffset=+1]
14+
include::modules/microshift-config-nodeport-limits.adoc[leveloffset=+1]
File renamed without changes.
Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * microshift/using-config-tools.adoc
4+
5+
:_content-type: CONCEPT
6+
[id="microshift-nodeport-range-limits_{context}"]
7+
= Extending the NodePort service range
8+
9+
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.
10+
11+
[IMPORTANT]
12+
NodePorts can overlap with system ports, causing a malfunction of the system or {product-title}.
13+
14+
Considerations when configuring the NodePort service ranges:
15+
16+
* Do not create any NodePort service without an explicit `nodePort` selection. In this case, the port is assigned randomly by the `kube-apiserver`.
17+
18+
* Do not create any NodePort service for any system service port, {product-title} port, or other services you expose on your device `HostNetwork`.
19+
20+
* Table one specifies ports to avoid when extending the port range:
21+
22+
.Ports to avoid.
23+
[cols="2",options="header"]
24+
|===
25+
|Port
26+
|Description
27+
28+
|22/tcp
29+
|SSH port
30+
31+
|80/tcp
32+
|OpenShift Router HTTP endpoint
33+
34+
|443/tcp
35+
|OpenShift Router HTTPS endpoint
36+
37+
|1936/tcp
38+
|Metrics service for the openshift-router, not exposed today
39+
40+
|2379/tcp
41+
|etcd port
42+
43+
|2380/tcp
44+
|etcd port
45+
46+
|6443
47+
|kubernetes API
48+
49+
|8445/tcp
50+
|openshift-route-controller-manager
51+
52+
|9537/tcp
53+
|cri-o metrics
54+
55+
|10250/tcp
56+
|kubelet
57+
58+
|10248/tcp
59+
|kubelet healthz port
60+
61+
|10259/tcp
62+
|kube scheduler
63+
|===

0 commit comments

Comments
 (0)