Skip to content

Commit

Permalink
Mention the difference in service lb label for RKE2 (#275)
Browse files Browse the repository at this point in the history
Signed-off-by: Derek Nola <derek.nola@suse.com>
  • Loading branch information
dereknola authored Oct 29, 2024
1 parent 9af9697 commit e50a85e
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion docs/networking/networking_services.md
Original file line number Diff line number Diff line change
Expand Up @@ -120,4 +120,8 @@ To disable the NGINX ingress controller, start each server with the `disable: rk

Kubernetes Services can be of type LoadBalancer but it requires an external load balancer controller to implement things correctly and for example,provide the external-ip. RKE2 can optionally deploy a load balancer controller known as [ServiceLB](https://github.com/k3s-io/klipper-lb) that uses available host ports. For more information, please read the following [link](https://docs.k3s.io/networking/networking-services#service-load-balancer).

To enable serviceLB, use the flag `--serviceLB` when deploying RKE2
:::tip
When looking at the K3s documentation, use the label `svccontroller.rke2.cattle.io` instead of `svccontroller.k3s.cattle.io` where applicable.
:::

To enable serviceLB, use the flag `--serviceLB` when deploying RKE2.

0 comments on commit e50a85e

Please sign in to comment.