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

updates based on Alena's feedback

Browse Source
This commit is contained in:
Mark Bishop
2018-07-20 14:46:27 -07:00
parent 84ec84ddfa
commit 4d8bda9c13
1 changed files with 20 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/kubernetes-in-rancher/load-balancers-and-ingress/_index.md
+20 -6
View File
@@ -5,7 +5,7 @@ weight: 3040
Within Rancher, you can setup load balancers and ingress controllers to redirect service requests.
### Load Balancers
## Load Balancers
After you launch an application, the app is only available within the cluster. It can't be reached from outside the cluster.
@@ -18,13 +18,27 @@ Rancher supports two types of load balancers:
For more information, see [load balancers]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/load-balancers-and-ingress/load-balancers).
#### Ingress
### Load Balancer Limitations
Load Balancers can only handle one IP address per service, which means if you run multiple services in your cluster, you must have a load balancer for each service. Running multiples load balancers can be expensive.
Load Balancers have a couple of limitations you should be aware of:
To address this issue, you can set up an ingress. Ingress is a controller that sits behind a load balancer. When the load balancer receives a request for one of the services running in your cluster, the load balancer passes it to your Ingress. Ingress then routes the request to the correct service based on service subdomains or path rules that you've configured.
- Load Balancers can only handle one IP address per service, which means if you run multiple services in your cluster, you must have a load balancer for each service. Running multiples load balancers can be expensive.
Ingress can provide other functionality as well, such as SSL termination and name-based virtual hosting.
- If you want to use a load balancer with a Hosted Kubernetes cluster (i.e., clusters hosted in GKE, EKS, or AKS), you must host your load balancer with the same cloud provider. For more information, view the following compatibility tables:
- [Cloud Support for Layer-4 Load Balancing]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/load-balancers-and-ingress/load-balancers/#cloud-support-for-layer-4-load-balancing)
- [Cloud Support for Layer-7 Load Balancing]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/load-balancers-and-ingress/load-balancers/#cloud-support-for-layer-7-load-balancing)
## Ingress
As mentioned in the limitations above, using a load balancer per service can be expensive. You can get around this issue using an ingress.
Ingress is a load balancer that works in conjunction with one or more ingress controllers to dynamically route service request. When the ingress receives a request, the ingress controller(s) in your cluster program the ingress to direct the request to the correct service based on service subdomains or path rules that you've configured.
Your ingress can either reside within your cluster or externally. Ingress and ingress controllers residing in RKE-launcher clusters are powered by [Nginx](https://www.nginx.com/).
Ingress can provide other functionality as well, such as SSL termination, name-based virtual hosting, and more.
- For more information on how to setup ingress in Rancher, see [Ingress]({{< baseurl >}}/rancher/v2.x/en/kubernetes-in-rancher/load-balancers-and-ingress/ingress).
- For complete information about ingress, see the [Kubernetes Ingress Documentation](https://kubernetes.io/docs/concepts/services-networking/ingress/)
- For complete information about ingress and ingress controllers, see the [Kubernetes Ingress Documentation](https://kubernetes.io/docs/concepts/services-networking/ingress/)