docker/docker-mailserver
1
0
Fork 0
mirror of https://github.com/tomav/docker-mailserver.git synced 2024-06-26 19:25:53 +02:00
Code Issues Releases Wiki Activity

add one more requirement for using PROXY protocol

Browse Source
This commit is contained in:
georglauterbach 2024-03-09 17:38:18 +01:00
parent 8edf55edab
commit edf0a623e4
No known key found for this signature in database
GPG Key ID: F367F7C43C118578
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -500,7 +500,7 @@ The major problem with exposing DMS to the outside world in Kubernetes is to [pr
- :-1: requires the node to have a dedicated, publicly routable IP address
- :-1: limited to the node with the dedicated IP address
- :-1: it is not possible to access DMS via other cluster nodes, only via the node that DMS was deployed on
- :-1: every Port within the container is exposed on the host side
- :-1: every port within the container is exposed on the host side
=== "Using the PROXY Protocol"
@ -523,6 +523,7 @@ The major problem with exposing DMS to the outside world in Kubernetes is to [pr
- :+1: preserves the origin IP address of clients (_which is crucial for DNS related checks_);
- :+1: aligns with a best practice for Kubernetes by using a dedicated ingress to route external traffic to the k8s cluster (_which additionally benefits from the flexibility of routing rules_); and
- :+1: avoids the restraint of a single [node][Kubernetes-nodes] (_as a workaround to preserve the original client IP_).
- :point_right: requires a proxy (if you do not already have one, e.g. as an ingress, you will need to set up one)
- :-1: added complexity
- on the manifest side: changing the DMS configured `Service`
- on DMS' side: changing the Postfix and Dovecot configuration