updating note

content/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/_index.md

@@ -26,7 +26,7 @@ View hardware and software requirements for each of your cluster nodes in [Requi
 
 RKE, the installer that provisions your air gapped cluster, will configure an Ingress controller pod on each of your nodes. The Ingress controller pods are bound to ports TCP/80 and TCP/443 on the host network and are the entry point for HTTPS traffic to the Rancher server.
 
-Configure a load balancer as a basic Layer 4 TCP forwarder. This load balancer should be dedicated strictly to Rancher traffic and no other applications (if you need load balancing for another application, provision a new cluster and load balancer for the app). The exact configuration will vary depending on your environment. 
+Configure a load balancer as a basic Layer 4 TCP forwarder. The exact configuration will vary depending on your environment. 
 
 **Load Balancer Configuration Samples:**
 

content/rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md

@@ -17,7 +17,7 @@ View the OS requirements for RKE at [RKE Requirements]({{< baseurl >}}/rke/v0.1.
 
 RKE will configure an Ingress controller pod, on each of your nodes. The Ingress controller pods are bound to ports TCP/80 and TCP/443 on the host network and are the entry point for HTTPS traffic to the Rancher server.
 
-Configure a load balancer as a basic Layer 4 TCP forwarder. This load balancer should be dedicated strictly to Rancher traffic and no other applications (if you need load balancing for another application, provision a new cluster and load balancer for the app). The exact configuration will vary depending on your environment. 
+Configure a load balancer as a basic Layer 4 TCP forwarder. The exact configuration will vary depending on your environment. 
 
 #### Examples
 

content/rancher/v2.x/en/k8s-in-rancher/load-balancers-and-ingress/_index.md

@@ -41,5 +41,9 @@ Your load balancer can either reside within your cluster or externally. Ingress
 
 Ingress can provide other functionality as well, such as SSL termination, name-based virtual hosting, and more.
 
+>**Using Rancher in a High Availability Configuration?**
+>
+>Refrain from adding an Ingress to the `local` cluster. The Nginx Ingress Controller that Rancher uses acts as a global load balancer for _all_ clusters managed by Rancher, including the `local` cluster.  Therefore, when users try to access an application, your Rancher connection may drop due to the Nginx configuration being reloaded. We recommend working around this issue by deploying applications only in clusters that you launch using Rancher.
+
 - For more information on how to setup ingress in Rancher, see [Ingress]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/load-balancers-and-ingress/ingress).
 - For complete information about ingress and ingress controllers, see the [Kubernetes Ingress Documentation](https://kubernetes.io/docs/concepts/services-networking/ingress/)

content/rancher/v2.x/en/k8s-in-rancher/load-balancers-and-ingress/ingress/_index.md

@@ -7,6 +7,15 @@ aliases:
 
 Ingress can be added for workloads to provide load balancing, SSL termination and host/path based routing.
 
+>**Using Rancher in a High Availability Configuration?**
+>
+>Refrain from adding an Ingress to the `local` cluster. The Nginx Ingress Controller that Rancher uses acts as a global load balancer for _all_ clusters managed by Rancher, including the `local` cluster.  Therefore, when users try to access an application, your Rancher connection may drop due to the Nginx configuration being reloaded. We recommend working around this issue by deploying applications only in clusters that you launch using Rancher.
+><figcaption>Don't add an Ingress to the <code>local</code> cluster.</figcaption>
+>![Don't Add Ingress]({{< baseurl >}}/img/rancher/no-ingress.png)
+
+
+
+
 1. From the **Global** view, open the project that you want to add ingress to.
 
 1. Select the **Load Balancing** tab. Then click **Add Ingress**.

content/rancher/v2.x/en/k8s-in-rancher/load-balancers-and-ingress/load-balancers/_index.md

@@ -42,6 +42,10 @@ RKE on DigitalOcean                           | Nginx Ingress Controller
 RKE on vSphere                                | Nginx Ingress Controller
 RKE on Custom Hosts<br/>(e.g. bare-metal servers) | Nginx Ingress Controller
 
+>**Using Rancher in a High Availability Configuration?**
+>
+>Refrain from adding an Ingress to the `local` cluster. The Nginx Ingress Controller that Rancher uses acts as a global load balancer for _all_ clusters managed by Rancher, including the `local` cluster.  Therefore, when users try to access an application, your Rancher connection may drop due to the Nginx configuration being reloaded. We recommend working around this issue by deploying applications only in clusters that you launch using Rancher.
+
 ### Host Names in Layer-7 Load Balancer
 
 Some cloud-managed layer-7 load balancers (such as the ALB ingress controller on AWS) expose DNS addresses for ingress rules. You need to map (via CNAME) your domain name to the DNS address generated by the layer-7 load balancer.
@@ -55,8 +59,6 @@ The benefit of using xip.io is that you obtain a working entrypoint URL immediat
 
 ## Related Links
 
-#### External Links
-
 - [Create an External Load Balancer](https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/)
 
 #### Tutorials