-
Notifications
You must be signed in to change notification settings - Fork 826
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 to the helm template for agones-allocator service #2476
Add NodePort to the helm template for agones-allocator service #2476
Conversation
/cc @roberthbailey |
Build Failed 😱 Build Id: acdc7973-84ca-4a21-8eac-fc04204783c8 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Build Failed 😱 Build Id: fac8cc61-3d53-4f58-81a0-2acd23a10173 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Looks like a flake, will run again when it gets fixed. #2479 |
install/helm/agones/values.yaml
Outdated
@@ -164,11 +164,13 @@ agones: | |||
port: 443 | |||
portName: https | |||
targetPort: 8443 | |||
nodePort: 0 |
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.
Two thoughts about this.
- Setting this to 0 seems like a bad default. If we are going to set it to an example value, it seems like it should be a port that would actually work if you just changed the
serviceType
above. - This file doesn't really have many comments, but it seems like if we are going to include a value here it is worth adding a comment that it will only be used if the service type is set to 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.
Thank you for the feedback.
-
I think it is okay to use 0. When I type
kubectl create service nodeport --help
, the nodePort parameter is described like this.(docker-desktop) ☁ ~ kubectl create service nodeport --help --node-port=0: Port used to expose the service on each node in a cluster.
This is because v1.ServiceSpec.ServicePort is using int32.
I found some examples that using
NodePort: 0
in the test code of kubectl withexpectErr: false
.It is a good idea to use an example NodePort with the default range of 30000-32767. However, it could make an error if the port is already taken by another Service.
-
Comments are added right behind the nodePort.
6227e98
to
73228fc
Compare
Build Failed 😱 Build Id: 570cbc55-3a10-434a-884a-d2d15a3ed182 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
Failed on
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jiwonaid, roberthbailey The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Build Succeeded 👏 Build Id: 964ed8a6-a7f8-4dfd-bcb3-b2da9e95b46e The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
What type of PR is this?
/kind feature
What this PR does / Why we need it:
To support type: NodePort for agones dev environment.
Which issue(s) this PR fixes:
Closes #1699
Special notes for your reviewer:
Hello, this is my second pull request.
May I freely select between normal issues and
good first issue
? Is it okay to solve multiple good first issues?