From 4dfe11e470230891799ad06d949222181b864562 Mon Sep 17 00:00:00 2001
From: georglauterbach <44545919+georglauterbach@users.noreply.github.com>
Date: Sat, 9 Mar 2024 17:24:33 +0100
Subject: [PATCH] drop content that is not relevant or incorrect

The scaling-issue is incorrect here, because there is no actual relation
to the `Service`. Whether not the Origin IP is preserved is covered
later too - no need to make the reader confused at this point.
---
 docs/content/config/advanced/kubernetes.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/content/config/advanced/kubernetes.md b/docs/content/config/advanced/kubernetes.md
index 861df66d..88fde5a0 100644
--- a/docs/content/config/advanced/kubernetes.md
+++ b/docs/content/config/advanced/kubernetes.md
@@ -110,7 +110,7 @@ When you do not want to or you cannot use Helm, below is a simple starting point
 
     A [`Service`][Kubernetes-network-service] is required for getting the traffic to the pod itself. It configures a load balancer with the ports you'll need.
 
-    The configuration for a `Service` affects if the original IP from a connecting client is preserved (_this is important_). [More about this further down below](#exposing-your-mail-server-to-the-outside-world). The configuration covered below does keep the original client IP, but you will not be able to scale this way. Thus this approach is only suitable to support a single instance of DMS.
+    The configuration for a `Service` affects if the original IP from a connecting client is preserved (_this is important_). [More about this further down below](#exposing-your-mail-server-to-the-outside-world).
 
     ```yaml
     ---