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
Remove hardcoded port #30
base: main
Are you sure you want to change the base?
Conversation
NodePort is able to dynamically grab a port to bind to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you want to use nodePort
without specifying a port, then rather only set the port when type is NodePort
AND nodeport.port
is defined.
@@ -18,9 +18,6 @@ spec: | |||
port: {{ .Values.service.servicePort }} | |||
targetPort: 3000 | |||
protocol: TCP | |||
{{- if eq .Values.service.type "NodePort" }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is backwards breaking and the NodePort should stay configurable.
The port is not hardcoded but set by default, IF service type is "NodePort" (which by default is "ClusterIP").
@@ -35,9 +35,6 @@ service: | |||
## from within the cluster. To expose externally, consider a "NodePort" or "LoadBalancer" service. | |||
type: ClusterIP | |||
## Further configuration if service is of type "NodePort" | |||
nodePort: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This must stay, but may be commented out as it is only used when type: NodePort
@dsloanather do you still want this contribution to be considered? Do you want to make the suggested changes? |
NodePort is able to dynamically grab a port to bind to