feat: Added support for NodePort port numbers configuration #286
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #28
Relates to fastlorenzo#25
This PR:
front.externalService.type=NodePort
As I commented on #268 (comment), using NodePort numbers < 1024 requires configuring the cluster in a way that is not allowed by many providers.
I think that admins that want to expose mail services on the default port directly on their Kubernetes nodes should use
front.hostPort.enabled=true
instead. NodePort services should be preferred when using an external load balancer.My personal Mailu instance is a "2 nodes cluster + NodePort service + haproxy" setup (for now, I have disabled
externalService
in Helm and added my ownService
resource). It took me some digging to configure all of this properly. I started reorganizing my personal notes into a piece of documentation : https://github.com/bidord/mailu-helm-charts/blob/feat-add-documentation-for-nodeport/mailu/README.md#running-behind-an-external-load-balancer-with-a-nodeport-service Tell me if you are interested in me adding it to this PR.