public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-14 00:53:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

updates to note

Browse Source
This commit is contained in:
Mark Bishop
2018-12-20 13:11:44 -07:00
parent f37f64d2e7
commit 8ecb8eea3d
4 changed files with 7 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/installation/air-gap-high-availability/provision-hosts/_index.md
+4 -1
View File
@@ -26,7 +26,10 @@ 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. 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 1) dedicating the `local` cluster to Rancher and no other apps and 2) deploying applications only in clusters that you launch using Rancher.
**Load Balancer Configuration Samples:**
content/rancher/v2.x/en/installation/ha/create-nodes-lb/_index.md
+3
View File
@@ -19,6 +19,9 @@ RKE will configure an Ingress controller pod, on each of your nodes. The Ingress
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 1) dedicating the `local` cluster to Rancher and no other apps and 2) deploying applications only in clusters that you launch using Rancher.
#### Examples
* [NGINX]({{< baseurl >}}/rancher/v2.x/en/installation/ha/create-nodes-lb/nginx/)
content/rancher/v2.x/en/k8s-in-rancher/load-balancers-and-ingress/ingress/_index.md
-9
View File
@@ -7,15 +7,6 @@ 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
-4
View File
@@ -42,10 +42,6 @@ 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.