Fix links and formatting

2026-09-25 20:48:11 +00:00 · 2022-09-15 17:48:58 +08:00
parent 5a3bfa4271
commit 6f187bee01
31 changed files with 47 additions and 2 deletions
@@ -21,6 +21,7 @@ This procedure walks you through setting up a 3-node cluster using the Rancher K
 In a Kubernetes setup that uses a layer 4 load balancer, the load balancer accepts Rancher client connections over the TCP/UDP protocols (i.e., the transport level). The load balancer then forwards these connections to individual cluster nodes without reading the request itself. Because the load balancer cannot read the packets it's forwarding, the routing decisions it can make are limited.

 <sup>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</sup>
+
 ![High-availability Kubernetes installation of Rancher](/img/ha/rancher2ha.svg)

 <br/>
@@ -22,6 +22,7 @@ This procedure walks you through setting up a 3-node cluster using the Rancher K
 In an Kubernetes setup that uses a layer 7 load balancer, the load balancer accepts Rancher client connections over the HTTP protocol (i.e., the application level). This application-level access allows the load balancer to read client requests and then redirect to them to cluster nodes using logic that optimally distributes load.

 <sup>Kubernetes Rancher install with layer 7 load balancer, depicting SSL termination at load balancer</sup>
+
 ![Rancher HA](/img/ha/rancher2ha-l7.svg)

 ## 1. Provision Linux Hosts
@@ -28,6 +28,7 @@ This procedure walks you through setting up a 3-node cluster with Rancher Kubern
 - The Ingress controller will forward traffic to port TCP/80 on the pod in the Rancher deployment.

 <figcaption>Kubernetes Rancher install with layer 4 load balancer, depicting SSL termination at ingress controllers</figcaption>
+
 ![High-availability Kubernetes Install](/img/ha/rancher2ha.svg)
 <sup>Kubernetes Rancher install with Layer 4 load balancer (TCP), depicting SSL termination at ingress controllers</sup>