docker
/
docker-mailserver
mirror of https://github.com/tomav/docker-mailserver.git
1
0
Fork 0
Code Issues Releases Wiki Activity

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.
This commit is contained in:
georglauterbach 2024-03-09 17:24:33 +01:00
parent a6d87157ae
commit 4dfe11e470
No known key found for this signature in database
GPG Key ID: F367F7C43C118578
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/content/config/advanced/kubernetes.md
View File

@ -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
---