Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[MailDev] Separate SMTP and web ports on Pod and k8s Service #1036

Merged
merged 1 commit into from
Feb 10, 2024

Conversation

redzioch
Copy link

@redzioch redzioch commented Feb 5, 2024

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 default 1025. I do not know for what reasons this happens - from a pure Debian image I had no problems connecting to MailDev SMTP service on 1025.

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 k8s Service ports, exposed to other applications.

I have added two more variables to values.yaml: services.smtp.podPort (with default value 1025) and services.web.podPort (with default value 1080).

This change is backwards compatible and allows to set any service ports including 25 or 80.

@redzioch redzioch changed the title Separate SMTP and web ports on Pod and k8s Service [MailDev] Separate SMTP and web ports on Pod and k8s Service Feb 5, 2024
@christianhuth christianhuth merged commit c83c7eb into christianhuth:main Feb 10, 2024
2 of 3 checks passed
@christianhuth
Copy link
Owner

Thanks for your contribution @redzioch!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants