From 38d520bc14429fbd0c0b57ec51740c8756d9bdf3 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 10 Aug 2020 09:46:53 -0700 Subject: [PATCH] Update content/k3s/latest/en/networking/_index.md Co-authored-by: Brad Davidson --- content/k3s/latest/en/networking/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/k3s/latest/en/networking/_index.md b/content/k3s/latest/en/networking/_index.md index a5c7741212e..babd38559a9 100644 --- a/content/k3s/latest/en/networking/_index.md +++ b/content/k3s/latest/en/networking/_index.md @@ -37,7 +37,7 @@ To disable it, start each server with the `--disable traefik` option. # Service Load Balancer -Any service load balancer (LB) can be leveraged in your Kubernetes cluster. K3s provides a Service LB that uses available host ports. +Any service load balancer (LB) can be leveraged in your Kubernetes cluster. K3s provides a load balancer known as [Klipper Load Balancer](https://github.com/rancher/klipper-lb) that uses available host ports. Upstream Kubernetes allows a Service of type LoadBalancer to be created, but doesn't include the implementation of the LB. Some LB services require a cloud provider such as Amazon EC2 or Microsoft Azure. By contrast, the K3s service LB makes it possible to use an LB service without a cloud provider.