Merge pull request #1045 from MBishop17/load-balancer-caveat

adding note that Rancher load balancer shouldn't serve double duty wi…

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

@@ -28,6 +28,9 @@ RKE, the installer that provisions your air gapped cluster, will configure an In
 
 Configure a load balancer as a basic Layer 4 TCP forwarder. The exact configuration will vary depending on your environment.
 
+>**Important:**
+>Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
+
 **Load Balancer Configuration Samples:**
 
 - [NGINX]({{< baseurl >}}/rancher/v2.x/en/installation/ha/create-nodes-lb/nginx)

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

@@ -17,7 +17,10 @@ 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. 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. 
+
+>**Important:**
+>Do not use this load balancer (i.e, the `local` cluster Ingress) to load balance applications other than Rancher following installation. Sharing this Ingress with other applications may result in websocket errors to Rancher following Ingress configuration reloads for other apps. We recommend dedicating the `local` cluster to Rancher and no other applications.
 
 #### 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/load-balancers/_index.md

@@ -55,8 +55,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