From ec0afcf0b258ddc743b3b072605fc54c0939bd42 Mon Sep 17 00:00:00 2001 From: Laurence van der Krieken Date: Wed, 7 Aug 2019 10:52:54 +0200 Subject: [PATCH] Fix small typo in load-balancing documentation --- content/rancher/v2.x/en/v1.6-migration/load-balancing/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/v1.6-migration/load-balancing/_index.md b/content/rancher/v2.x/en/v1.6-migration/load-balancing/_index.md index c34f46f1cca..b2996c8d41f 100644 --- a/content/rancher/v2.x/en/v1.6-migration/load-balancing/_index.md +++ b/content/rancher/v2.x/en/v1.6-migration/load-balancing/_index.md @@ -26,7 +26,7 @@ If you encounter the `output.txt` text below after parsing your v1.6 Compose fil By default, Rancher v2.x replaces the v1.6 load balancer microservice with the native [Kubernetes Ingress](https://kubernetes.io/docs/concepts/services-networking/ingress/), which is backed by NGINX Ingress Controller for layer 7 load balancing. By default, Kubernetes Ingress only supports the HTTP and HTTPS protocols, not TCP. Load balancing is limited to these two protocols when using Ingress. -> **TCP Required?** See [TCP Load Balancing Optionsl](#tcp-load-balancing-options) +> **TCP Required?** See [TCP Load Balancing Options](#tcp-load-balancing-options) ## Load Balancer Deployment