-
Notifications
You must be signed in to change notification settings - Fork 71
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
Make mongo-express service.nodePort configurable #37
Comments
This is a change i know i need to do, thanks to recall me :-) |
@DanielBican I've misread your need. I thought you want to customize service nodePort. What is your use case of having a custom targetPort? |
You got it right actually. I need a customizable nodePort. Should I edit
the issue title and description?
…On Thu, Sep 3, 2020 at 10:37 PM sebastien-prudhomme < ***@***.***> wrote:
@DanielBican <https://github.com/DanielBican> I've misread your need. I
thought you want to customize service nodePort. What is your use case of
having a custom targetPort?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABNMS5AMUDYQKQBCWDCWNWLSD7WATANCNFSM4QUOXGWQ>
.
|
sebastien-prudhomme
changed the title
Make mongo-express service.targetPort configurable
Make mongo-express service.nodePort configurable
Sep 4, 2020
This is fixed in #38 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am using mongo-express for a personal project and I am really happy with it. Great work:)
There is a small enhancement that I would benefit from, namely to make the service.targetPort configurable. I am using service.type=NodePort.
The text was updated successfully, but these errors were encountered: