-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add nodeport/ingress service options #1
Comments
Additionally it would be nice to have the option of creating an ingress for the control plane and the gateway. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently 'control-plane-deployment.yaml' gives the primary container the following option for port numbering:
The 'control-plane-service.yaml' uses the same port value to set the service.
If I set the 'type' to NodePort, but can't set a NodePort value then K8s will choose one for me. But I have no way of setting the container port so it will default to "8090". Which renders the service unhealthy and the control plane pod inaccessible.
The text was updated successfully, but these errors were encountered: