[MailDev] Separate SMTP and web ports on Pod and k8s Service #1036
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.
I came across a case that on some Docker images (eg.
openjdk
) there are problems with communication with SMTP server on non-standard ports, eg. MailDev default1025
. I do not know for what reasons this happens - from a pure Debian image I had no problems connecting to MailDev SMTP service on1025
.MaiDev can not be configured to use port like
25
- it runs as non-root user and therefore it is forbidden to use ports below 1024.As a workaround I propose to separate
Pod
ports (used by MailDev) and k8sService
ports, exposed to other applications.I have added two more variables to
values.yaml
:services.smtp.podPort
(with default value1025
) andservices.web.podPort
(with default value1080
).This change is backwards compatible and allows to set any service ports including
25
or80
.