fix: correct nodePort assignment for manager service #440
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Fixed a bug in
charts/dragonfly/templates/manager/manager-svc.yamlwhere the configured nodePort was incorrectly applied to the gRPC port (65003) instead of the REST/UI port (8080).I moved the nodePort conditional block to the correct port definition (http-rest) in the Service manifest.
Related Issue
#438
Motivation and Context
When configuring
manager.service.nodePortin values.yaml, the expectation is to expose the Manager Console (UI) on that specific port. Previously, this configuration was applied to the gRPC port, causing the UI to be assigned a random NodePort instead. This change ensures the UI is accessible on the user-defined port.