diff --git a/versioned_docs/version-2.0-2.4/installation/resources/advanced/helm2/create-nodes-lb/nlb/nlb.md b/versioned_docs/version-2.0-2.4/installation/resources/advanced/helm2/create-nodes-lb/nlb/nlb.md
index 4f15be04556..f75a1a2ef96 100644
--- a/versioned_docs/version-2.0-2.4/installation/resources/advanced/helm2/create-nodes-lb/nlb/nlb.md
+++ b/versioned_docs/version-2.0-2.4/installation/resources/advanced/helm2/create-nodes-lb/nlb/nlb.md
@@ -55,15 +55,15 @@ Timeout (Advanced) | `6 seconds`
Interval (Advanced) | `10 second`
Success codes | `200-399`
-
+***
**Screenshot Target group TCP port 443 settings**
{{< img "/img/rancher/ha/nlb/create-targetgroup-443.png" "Target group 443">}}
-
+***
**Screenshot Target group TCP port 443 Advanced settings**
{{< img "/img/rancher/ha/nlb/create-targetgroup-443-advanced.png" "Target group 443 Advanced">}}
-
+***
Click **Create target group** to create the second target group, regarding TCP port 80.
@@ -87,15 +87,15 @@ Timeout (Advanced) | `6 seconds`
Interval (Advanced) | `10 second`
Success codes | `200-399`
-
+***
**Screenshot Target group TCP port 80 settings**
{{< img "/img/rancher/ha/nlb/create-targetgroup-80.png" "Target group 80">}}
-
+***
**Screenshot Target group TCP port 80 Advanced settings**
{{< img "/img/rancher/ha/nlb/create-targetgroup-80-advanced.png" "Target group 80 Advanced">}}
-
+***
## Register Targets
@@ -107,12 +107,12 @@ Select the target group named **rancher-tcp-443**, click the tab **Targets** and
Select the instances (Linux nodes) you want to add, and click **Add to registered**.
-
+***
**Screenshot Add targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/add-targets-targetgroup-443.png" "Add targets to target group 443">}}
-
+***
**Screenshot Added targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/added-targets-targetgroup-443.png" "Added targets to target group 443">}}
@@ -138,8 +138,8 @@ Use Amazon's Wizard to create an Network Load Balancer. As part of this process,
- Name: `rancher`
- Scheme: `internal` or `internet-facing`
-
- The Scheme that you choose for your NLB is dependent on the configuration of your instances/VPC. If your instances do not have public IPs associated with them, or you will only be accessing Rancher internally, you should set your NLB Scheme to `internal` rather than `internet-facing`.
+
+ The Scheme that you choose for your NLB is dependent on the configuration of your instances/VPC. If your instances do not have public IPs associated with them, or you will only be accessing Rancher internally, you should set your NLB Scheme to `internal` rather than `internet-facing`.
- **Listeners**
Add the **Load Balancer Protocols** and **Load Balancer Ports** below.
diff --git a/versioned_docs/version-2.0-2.4/installation/resources/advanced/helm2/rke-add-on/layer-4-lb/nlb/nlb.md b/versioned_docs/version-2.0-2.4/installation/resources/advanced/helm2/rke-add-on/layer-4-lb/nlb/nlb.md
index c8b155bb6c2..be079813917 100644
--- a/versioned_docs/version-2.0-2.4/installation/resources/advanced/helm2/rke-add-on/layer-4-lb/nlb/nlb.md
+++ b/versioned_docs/version-2.0-2.4/installation/resources/advanced/helm2/rke-add-on/layer-4-lb/nlb/nlb.md
@@ -62,15 +62,15 @@ Timeout (Advanced) | `6 seconds`
Interval (Advanced) | `10 second`
Success codes | `200-399`
-
+***
**Screenshot Target group TCP port 443 settings**
{{< img "/img/rancher/ha/nlb/create-targetgroup-443.png" "Target group 443">}}
-
+***
**Screenshot Target group TCP port 443 Advanced settings**
{{< img "/img/rancher/ha/nlb/create-targetgroup-443-advanced.png" "Target group 443 Advanced">}}
-
+***
Click **Create target group** to create the second target group, regarding TCP port 80.
@@ -94,15 +94,15 @@ Timeout (Advanced) | `6 seconds`
Interval (Advanced) | `10 second`
Success codes | `200-399`
-
+***
**Screenshot Target group TCP port 80 settings**
{{< img "/img/rancher/ha/nlb/create-targetgroup-80.png" "Target group 80">}}
-
+***
**Screenshot Target group TCP port 80 Advanced settings**
{{< img "/img/rancher/ha/nlb/create-targetgroup-80-advanced.png" "Target group 80 Advanced">}}
-
+***
## Register Targets
@@ -114,12 +114,12 @@ Select the target group named **rancher-tcp-443**, click the tab **Targets** and
Select the instances (Linux nodes) you want to add, and click **Add to registered**.
-
+***
**Screenshot Add targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/add-targets-targetgroup-443.png" "Add targets to target group 443">}}
-
+***
**Screenshot Added targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/added-targets-targetgroup-443.png" "Added targets to target group 443">}}
diff --git a/versioned_docs/version-2.0-2.4/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md b/versioned_docs/version-2.0-2.4/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md
index 603fe9f7a2a..f34ca57b1ae 100644
--- a/versioned_docs/version-2.0-2.4/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md
+++ b/versioned_docs/version-2.0-2.4/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md
@@ -101,12 +101,12 @@ Select the target group named **rancher-tcp-443**, click the tab **Targets** and
Select the instances (Linux nodes) you want to add, and click **Add to registered**.
-
+***
**Screenshot Add targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/add-targets-targetgroup-443.png" "Add targets to target group 443">}}
-
+***
**Screenshot Added targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/added-targets-targetgroup-443.png" "Added targets to target group 443">}}
@@ -175,7 +175,7 @@ After AWS creates the NLB, click **Close**.
K3s and RKE Kubernetes clusters handle health checks differently because they use different Ingresses by default.
-For RKE Kubernetes clusters, NGINX Ingress is used by default, whereas for K3s Kubernetes clusters, Traefik is the default Ingress.
+For RKE Kubernetes clusters, NGINX Ingress is used by default, whereas for K3s Kubernetes clusters, Traefik is the default Ingress.
- **Traefik:** The health check path is `/ping`. By default `/ping` is always matched (regardless of Host), and a response from [Traefik itself](https://docs.traefik.io/operations/ping/) is always served.
- **NGINX Ingress:** The default backend of the NGINX Ingress controller has a `/healthz` endpoint. By default `/healthz` is always matched (regardless of Host), and a response from [`ingress-nginx` itself](https://github.com/kubernetes/ingress-nginx/blob/0cbe783f43a9313c9c26136e888324b1ee91a72f/charts/ingress-nginx/values.yaml#L212) is always served.
diff --git a/versioned_docs/version-2.5/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md b/versioned_docs/version-2.5/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md
index 3f586b3b4f3..8fb64ceb549 100644
--- a/versioned_docs/version-2.5/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md
+++ b/versioned_docs/version-2.5/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md
@@ -102,12 +102,12 @@ Select the target group named **rancher-tcp-443**, click the tab **Targets** and
Select the instances (Linux nodes) you want to add, and click **Add to registered**.
-
+***
**Screenshot Add targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/add-targets-targetgroup-443.png" "Add targets to target group 443">}}
-
+***
**Screenshot Added targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/added-targets-targetgroup-443.png" "Added targets to target group 443">}}
@@ -176,7 +176,7 @@ After AWS creates the NLB, click **Close**.
K3s and RKE Kubernetes clusters handle health checks differently because they use different Ingresses by default.
-For RKE Kubernetes clusters, NGINX Ingress is used by default, whereas for K3s Kubernetes clusters, Traefik is the default Ingress.
+For RKE Kubernetes clusters, NGINX Ingress is used by default, whereas for K3s Kubernetes clusters, Traefik is the default Ingress.
- **Traefik:** The health check path is `/ping`. By default `/ping` is always matched (regardless of Host), and a response from [Traefik itself](https://docs.traefik.io/operations/ping/) is always served.
- **NGINX Ingress:** The default backend of the NGINX Ingress controller has a `/healthz` endpoint. By default `/healthz` is always matched (regardless of Host), and a response from [`ingress-nginx` itself](https://github.com/kubernetes/ingress-nginx/blob/0cbe783f43a9313c9c26136e888324b1ee91a72f/charts/ingress-nginx/values.yaml#L212) is always served.
diff --git a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md
index 24eb4b4ca43..be1f6102b75 100644
--- a/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md
+++ b/versioned_docs/version-2.6/installation/resources/k8s-tutorials/infrastructure-tutorials/nlb/nlb.md
@@ -97,12 +97,12 @@ Select the target group named **rancher-tcp-443**, click the tab **Targets** and
Select the instances (Linux nodes) you want to add, and click **Add to registered**.
-
+***
**Screenshot Add targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/add-targets-targetgroup-443.png" "Add targets to target group 443">}}
-
+***
**Screenshot Added targets to target group TCP port 443**
{{< img "/img/rancher/ha/nlb/added-targets-targetgroup-443.png" "Added targets to target group 443">}}
@@ -171,7 +171,7 @@ After AWS creates the NLB, click **Close**.
K3s and RKE Kubernetes clusters handle health checks differently because they use different Ingresses by default.
-For RKE Kubernetes clusters, NGINX Ingress is used by default, whereas for K3s Kubernetes clusters, Traefik is the default Ingress.
+For RKE Kubernetes clusters, NGINX Ingress is used by default, whereas for K3s Kubernetes clusters, Traefik is the default Ingress.
- **Traefik:** The health check path is `/ping`. By default `/ping` is always matched (regardless of Host), and a response from [Traefik itself](https://docs.traefik.io/operations/ping/) is always served.
- **NGINX Ingress:** The default backend of the NGINX Ingress controller has a `/healthz` endpoint. By default `/healthz` is always matched (regardless of Host), and a response from [`ingress-nginx` itself](https://github.com/kubernetes/ingress-nginx/blob/0cbe783f43a9313c9c26136e888324b1ee91a72f/charts/ingress-nginx/values.yaml#L212) is always served.