diff --git a/content/rancher/v2.x/en/installation/references/_index.md b/content/rancher/v2.x/en/installation/references/_index.md
index b0dedf04dd4..2de9174d2eb 100644
--- a/content/rancher/v2.x/en/installation/references/_index.md
+++ b/content/rancher/v2.x/en/installation/references/_index.md
@@ -9,13 +9,13 @@ To operate properly, Rancher requires a number of ports to be open on Rancher no
## Rancher Nodes
-The following table lists the ports that need to be open to/from nodes that are running the `rancher/rancher` container ([Single Node Install]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install/)) or `cattle` deployment pods ([High Availability Install]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install/)).
+The following table lists the ports that need to be open to and from nodes that are running the `rancher/rancher` container ([Single Node Install]({{< baseurl >}}/rancher/v2.x/en/installation/single-node-install/)) or `cattle` deployment pods ([High Availability Install]({{< baseurl >}}/rancher/v2.x/en/installation/ha-server-install/)).
{{< ports-rancher-nodes >}}
## Kubernetes Cluster Nodes
-The required ports for cluster nodes vary across different methods for creating clusters.
+The ports required to be open for cluster nodes changes depending on how the cluster was launched. Each of the tabs below list the ports that need to be opened for different [cluster creation options]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/#cluster-creation-options).
>**Tip:**
>
@@ -23,7 +23,7 @@ The required ports for cluster nodes vary across different methods for creating
{{% tabs %}}
-{{% tab "IaaS Clusters" %}}
+{{% tab "Node Pools" %}}
The following table depicts the port requirements for [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/) with nodes created in an [Infrastructure Provider]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/).
@@ -34,7 +34,7 @@ The following table depicts the port requirements for [Rancher Launched Kubernet
{{% /tab %}}
-{{% tab "Custom Cluster" %}}
+{{% tab "Custom Nodes" %}}
The following table depicts the port requirements for [Rancher Launched Kubernetes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/) with [Custom Nodes]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/).
@@ -83,7 +83,7 @@ These ports are typically opened on your Kubernetes nodes, regardless of what ty
### Local Node Traffic
-Ports marked as `local traffic` in the above requirements (e.g. `9099/tcp`) are used for Kubernetes healthchecks (`livenessProbe` and`readinessProbe`).
+Ports marked as `local traffic` (i.e., `9099 TCP`) in the above requirements are used for Kubernetes healthchecks (`livenessProbe` and`readinessProbe`).
These healthchecks are executed on the node itself. In most cloud environments, this local traffic is allowed by default.
However, this traffic may be blocked when:
@@ -91,12 +91,11 @@ However, this traffic may be blocked when:
- You have applied strict host firewall policies on the node.
- You are using nodes that have multiple interfaces (multihomed).
-In these cases, you have to explicitly allow this traffic in your host firewall, or in case of public/private cloud hosted machines (i.e. AWS or OpenStack), in your security group configuration. Keep in mind that when using a security group as source or destination in your security group, explicitly opening ports only applies to the private interface of the nodes/instances.
+In these cases, you have to explicitly allow this traffic in your host firewall, or in case of public/private cloud hosted machines (i.e. AWS or OpenStack), in your security group configuration. Keep in mind that when using a security group as source or destination in your security group, explicitly opening ports only applies to the private interface of the nodes / instances.
### Rancher AWS EC2 security group
-When using the [AWS EC2 node driver]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/) to provision cluster nodes in Rancher
-you can choose to let Rancher create a Security Group called `rancher-nodes`. The following rules are automatically added to this Security Group.
+When using the [AWS EC2 node driver]({{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ec2/) to provision cluster nodes in Rancher, you can choose to let Rancher create a security group called `rancher-nodes`. The following rules are automatically added to this security group.
| Type | Protocol | Port Range | Source/Destination | Rule Type |
|-----------------|:--------:|:-----------:|------------------------|:---------:|
@@ -113,5 +112,3 @@ you can choose to let Rancher create a Security Group called `rancher-nodes`. Th
| Custom TCP Rule | TCP | 30000-32767 | 30000-32767 | Inbound |
| Custom UDP Rule | UDP | 30000-32767 | 30000-32767 | Inbound |
| All traffic | All | All | 0.0.0.0/0 | Outbound |
-
-----
\ No newline at end of file
diff --git a/layouts/shortcodes/ports-custom-nodes.html b/layouts/shortcodes/ports-custom-nodes.html
index 481ce789a97..9b9f06e10d8 100644
--- a/layouts/shortcodes/ports-custom-nodes.html
+++ b/layouts/shortcodes/ports-custom-nodes.html
@@ -18,108 +18,108 @@
|
|
|
- git.rancher.io (2):
35.160.43.145:32
35.167.242.46:32
52.33.59.17:32 |
+ git.rancher.io (2):
35.160.43.145:32
35.167.242.46:32
52.33.59.17:32 |
| etcd Plane Nodes |
- 443 TCP (3) |
- 2379 TCP |
+ 443 TCP (3) |
+ 2379 TCP |
|
|
- 443 TCP |
+ 443 TCP |
|
- | 2380 TCP |
+ 2380 TCP |
|
|
|
|
- 6443 TCP |
+ 6443 TCP |
|
|
- | 8472 UDP |
+ 8472 UDP |
|
- | 9099 TCP (4) |
+ 9099 TCP (4) |
|
|
|
| Control Plane Nodes |
- 443 TCP (3) |
- 2379 TCP |
+ 443 TCP (3) |
+ 2379 TCP |
|
|
- 443 TCP |
+ 443 TCP |
|
- | 2380 TCP |
+ 2380 TCP |
|
|
|
|
- 6443 TCP |
+ 6443 TCP |
|
|
- | 8472 UDP |
+ 8472 UDP |
|
- | 10250 TCP |
+ 10250 TCP |
|
|
- 9099 TCP (4) |
+ 9099 TCP (4) |
|
|
|
- 10254 TCP (4) |
+ 10254 TCP (4) |
|
|
| Worker Plane Nodes |
- 443 TCP (3) |
+ 443 TCP (3) |
|
- 6443 TCP |
+ 6443 TCP |
|
- 443 TCP |
+ 443 TCP |
|
- | 8472 UDP |
+ 8472 UDP |
|
|
|
- 9099 TCP (4) |
+ 9099 TCP (4) |
|
|
|
- 10254 TCP (4) |
+ 10254 TCP (4) |
|
| External Load Balancer (5) |
- 80 TCP |
+ 80 TCP |
|
|
|
@@ -127,7 +127,7 @@
|
- | 443 TCP (6) |
+ 443 TCP (6) |
|
|
|
@@ -136,19 +136,19 @@
| API / UI Clients |
- 80 TCP (3) |
+ 80 TCP (3) |
|
|
|
- 80 TCP
|
+ 80 TCP
|
|
- | 443 TCP (3) |
+ 443 TCP (3) |
|
|
|
- 443 TCP |
+ 443 TCP |
|
@@ -156,21 +156,21 @@
|
|
|
- 30000-32767 TCP/UDP
(nodeport) |
+ 30000-32767 TCP / UDP
(nodeport) |
|
|
|
|
- 80 TCP (Ingress) |
+ 80 TCP (Ingress) |
|
|
|
|
- 443 TCP (Ingress) |
+ 443 TCP (Ingress) |
|
|
diff --git a/layouts/shortcodes/ports-iaas-nodes.html b/layouts/shortcodes/ports-iaas-nodes.html
index 284a32a5b25..853c7a0e626 100644
--- a/layouts/shortcodes/ports-iaas-nodes.html
+++ b/layouts/shortcodes/ports-iaas-nodes.html
@@ -14,115 +14,115 @@
| Rancher Nodes (1) |
|
- 22 TCP |
+ 22 TCP |
|
- git.rancher.io (2):
35.160.43.145:32
35.167.242.46:32
52.33.59.17:32 |
+ git.rancher.io (2):
35.160.43.145:32
35.167.242.46:32
52.33.59.17:32 |
|
- 2376 TCP |
+ 2376 TCP |
|
| etcd Plane Nodes |
- 443 TCP (3) |
- 2379 TCP |
+ 443 TCP (3) |
+ 2379 TCP |
|
|
- 443 TCP |
+ 443 TCP |
|
- | 2380 TCP |
+ 2380 TCP |
|
|
|
|
- 6443 TCP |
+ 6443 TCP |
|
|
- | 8472 TCP |
+ 8472 UDP |
|
- | 9099 TCP (4) |
+ 9099 TCP (4) |
|
|
|
| Control Plane Nodes |
- 443 TCP (3) |
- 2379 TCP |
+ 443 TCP (3) |
+ 2379 TCP |
|
|
- 443 TCP |
+ 443 TCP |
|
- | 2380 TCP |
+ 2380 TCP |
|
|
|
|
- 6443 TCP |
+ 6443 TCP |
|
|
- | 8472 UDP |
+ 8472 UDP |
|
- | 10250 TCP |
+ 10250 TCP |
|
|
- 9099 TCP (4) |
+ 9099 TCP (4) |
|
|
|
- 10254 TCP (4) |
+ 10254 TCP (4) |
|
|
| Worker Plane Nodes |
- 443 TCP (3) |
+ 443 TCP (3) |
|
- 6443 TCP |
+ 6443 TCP |
|
- 443 TCP |
+ 443 TCP |
|
- | 8472 UDP |
+ 8472 UDP |
|
|
|
- 9099 TCP (4) |
+ 9099 TCP (4) |
|
|
|
- 10254 TCP (4) |
+ 10254 TCP (4) |
|
| External Load Balancer (5) |
- 80 TCP |
+ 80 TCP |
|
|
|
@@ -130,7 +130,7 @@
|
- | 443 TCP (6) |
+ 443 TCP (6) |
|
|
|
@@ -139,19 +139,19 @@
| API / UI Clients |
- 80 TCP (3) |
+ 80 TCP (3) |
|
|
|
- 80 TCP
|
+ 80 TCP
|
|
- | 443 TCP (3) |
+ 443 TCP (3) |
|
|
|
- 443 TCP |
+ 443 TCP |
|
@@ -159,21 +159,21 @@
|
|
|
- 30000-32767 TCP/UDP
(nodeport) |
+ 30000-32767 TCP / UDP
(nodeport) |
|
|
|
|
- 80 TCP (Ingress) |
+ 80 TCP (Ingress) |
|
|
|
|
- 443 TCP (Ingress) |
+ 443 TCP (Ingress) |
|
|
diff --git a/layouts/shortcodes/ports-imported-hosted.html b/layouts/shortcodes/ports-imported-hosted.html
index b8db5b42001..96eef6bec3c 100644
--- a/layouts/shortcodes/ports-imported-hosted.html
+++ b/layouts/shortcodes/ports-imported-hosted.html
@@ -12,35 +12,35 @@
| Rancher Nodes (1) |
|
- Kubernetes API
Endpoint Port (2) |
+ Kubernetes API
Endpoint Port (2) |
|
- git.rancher.io (3):
35.160.43.145/32
35.167.242.46/32
52.33.59.17/32 |
+ git.rancher.io (3):
35.160.43.145:32
35.167.242.46:32
52.33.59.17:32 |
| Hosted / Imported Cluster |
- 443 TCP (4)(5) |
+ 443 TCP (4)(5) |
|
- 443 TCP (5) |
+ 443 TCP (5) |
|
| External Load Balancer (5) |
- 80 TCP
443 TCP (6) |
+ 80 TCP
443 TCP (6) |
|
|
|
| API / UI Clients |
- 80 TCP (4)
443 TCP (4) |
+ 80 TCP (4)
443 TCP (4) |
|
- 80 TCP
443 TCP |
+ 80 TCP
443 TCP |
|
| Workload Client |
|
- Cluster / Provider Specific (7) |
+ Cluster / Provider Specific (7) |
|
|
diff --git a/layouts/shortcodes/ports-rancher-nodes.html b/layouts/shortcodes/ports-rancher-nodes.html
index ff28b8285af..30f7bda69ac 100644
--- a/layouts/shortcodes/ports-rancher-nodes.html
+++ b/layouts/shortcodes/ports-rancher-nodes.html
@@ -1,5 +1,4 @@
- Port Requirements for Hosted / Imported Clusters
| Protocol |