mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 12:38:05 +00:00
Adding blog on LB to the migration page
This commit is contained in:
@@ -51,6 +51,7 @@ More detailed information on Kubernetes concepts can be found in the
|
||||
- [4. Monitor Your Applications](#4-monitor-your-applications)
|
||||
- [5. Schedule Deployments](#5-schedule-deployments)
|
||||
- [6. Service Discovery](#6-service-discovery)
|
||||
- [7. Load Balancing](#7-load-balancing)
|
||||
<!--- [7. Load Balancing](#7-load-balancing)-->
|
||||
|
||||
|
||||
@@ -97,11 +98,11 @@ Rancher 1.6 provides service discovery within and across stacks using its own in
|
||||
|
||||
Blog Post: [From Cattle to Kubernetes—Service Discovery in Rancher 2.0](https://rancher.com/blog/2018/2018-09-04-service_discovery_2dot0/)
|
||||
|
||||
<!--## 7. Load Balancing
|
||||
## 7. Load Balancing
|
||||
|
||||
How to achieve TCP/HTTP load balancing and configure hostname/path-based routing in Rancher 2.0.
|
||||
|
||||
Blog Post: Coming soon!
|
||||
Blog Post: [From Cattle to Kubernetes-How to Load Balance Your Services in Rancher 2.0](https://rancher.com/blog/2018/2018-09-13-load-balancing-options-2dot0/)
|
||||
|
||||
In Rancher 1.6, a Load Balancer was used to expose your applications from within the Rancher environment for access externally. In Rancher 2.0, the concept is the same. There is a Load Balancer option to expose your services. In the language of Kubernetes, this function is more often referred to as an **Ingress**. In short, Load Balancer and Ingress play the same role.-->
|
||||
In Rancher 1.6, a Load Balancer was used to expose your applications from within the Rancher environment for external access. In Rancher 2.0, the concept is the same. There is a Load Balancer option to expose your services. In the language of Kubernetes, this function is more often referred to as an **Ingress**. In short, Load Balancer and Ingress play the same role.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user