From 51b783db2d7a5d00b1a7da94cbae82e8b4a2979f Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Wed, 5 Dec 2018 17:13:23 -0700 Subject: [PATCH] adding note that Rancher load balancer shouldn't serve double duty with for other apps --- .../air-gap-high-availability/provision-hosts/_index.md | 2 +- .../rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/_index.md b/content/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/_index.md index aa911439019..f91022f7f26 100644 --- a/content/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/_index.md +++ b/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. The exact configuration will vary depending on your environment. +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. **Load Balancer Configuration Samples:** diff --git a/content/rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md b/content/rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md index c9d51f538d3..e0f8947f17b 100644 --- a/content/rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md +++ b/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. The exact configuration will vary depending on your environment. +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. #### Examples