From 4a8254b1a5d0271d675ba0e7c1de0850d45d001b Mon Sep 17 00:00:00 2001 From: kirici <74684021+kirici@users.noreply.github.com> Date: Tue, 14 Oct 2025 15:18:36 +0200 Subject: [PATCH] docs: improve grammar, wording Signed-off-by: kirici <74684021+kirici@users.noreply.github.com> --- content/kubermatic/main/references/setup-checklist/_index.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/kubermatic/main/references/setup-checklist/_index.en.md b/content/kubermatic/main/references/setup-checklist/_index.en.md index c15eaa3e9..1f9ea817e 100644 --- a/content/kubermatic/main/references/setup-checklist/_index.en.md +++ b/content/kubermatic/main/references/setup-checklist/_index.en.md @@ -72,7 +72,7 @@ If no external load balancer is provided for the setup, we recommend [KubeLB](ht [![](kubelb.png)](https://docs.kubermatic.com/kubelb/v1.1/architecture/) -As frontend IPAM solution and IP announcement, KubeLB could use on-premise non-multi-tenant LB implementations like Cilium or MetalLB in Layer 2 ARP or BGP mode. (Also commercial Kubernetes conform implementation like [F5 Big IP](https://clouddocs.f5.com/products/connectors/k8s-bigip-ctlr/v1.0/#) would work). KubeLB will add the multi-tenant plus central DNS, Certificate and Ingress management. KubeLB deliver for each Kubernetes Cluster one tenant separated authentication token, what get used via the so called [KubeLB CCM](https://docs.kubermatic.com/kubelb/v1.1/installation/tenant-cluster/), what automatically get configured for KKP clusters. The KubeLB CCM is then handling service and node announcements. For Setups where multi-tenant automated LB is not required, direct [MetalLB](https://metallb.universe.tf/) or [Cilium](https://docs.cilium.io/) setups could be used as well. For the best performance and stability of the platform, we recommend to talk with our consultants to advise you what is the best fit for your environment. +As frontend IPAM solution and IP announcement, KubeLB could use on-premise non-multi-tenant LB implementations like Cilium or MetalLB in Layer 2 ARP or BGP mode (Commercial Kubernetes-conform implementations like [F5 Big IP](https://clouddocs.f5.com/products/connectors/k8s-bigip-ctlr/v1.0/#) would also work). KubeLB will add the multi-tenancy as well as central DNS, Certificate and Ingress management. KubeLB delivers one tenant-separated authentication token for each Kubernetes Cluster, which gets used via the so-called [KubeLB CCM](https://docs.kubermatic.com/kubelb/v1.1/installation/tenant-cluster/), which gets configured automatically for KKP clusters. The KubeLB CCM is then handling service and node announcements. For setups where multi-tenant automated LB is not required, direct [MetalLB](https://metallb.universe.tf/) or [Cilium](https://docs.cilium.io/) setups could be used as well. For the best performance and stability of the platform, we recommend talking to our consultants who may help you with finding the best fit for your environment. #### Layer 2 ARP Announcement