-
Notifications
You must be signed in to change notification settings - Fork 256
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 parameter to configure health endpoint port #1885
Add parameter to configure health endpoint port #1885
Conversation
✅ Deploy Preview for kubernetes-sigs-nfd ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
1e42741
to
4d56312
Compare
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.
minor nit, otherwise looks good imo
/cc @marquiz |
cmd/nfd-worker/main.go
Outdated
@@ -138,6 +136,8 @@ func initFlags(flagset *flag.FlagSet) (*worker.Args, *worker.ConfigOverrideArgs) | |||
"Do not publish feature labels") | |||
flagset.IntVar(&args.MetricsPort, "metrics", 8081, | |||
"Port on which to expose metrics.") | |||
flagset.IntVar(&args.GrpcHealthPort, "health", 8082, |
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.
same conversation as in master
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.
I kept the helm value as healthPort
, WDYT?
4d56312
to
1e7f6cf
Compare
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.
Thx for addressing my comments @tobiasgiese left a few minor nit based on the flag rename.
@@ -58,6 +58,7 @@ master: | |||
# be removed with it in a future release | |||
port: 8080 | |||
metricsPort: 8081 | |||
healthPort: 8082 |
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.
im ok with this being general health port while we map to grpc-health flag. later on it can map to a different flag if/once needed.
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.
xref #1885 (comment)
1e7f6cf
to
0bf26fb
Compare
0bf26fb
to
ed0ca13
Compare
Signed-off-by: Tobias Giese <tgiese@nvidia.com>
ed0ca13
to
53ddf08
Compare
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.
/lgtm
/retest |
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.
/lgtm
LGTM label has been added. Git tree hash: 5c6de8e5df03440483409e14c2ff4d531d817b07
|
/retest something is broken/flaky here 🤔
and
Seems like the community prow is broken currently |
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 @tobiasgiese for the contribution. Looks good to me
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adrianchiris, marquiz, tobiasgiese 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 |
/cherry-pick release-0.16 |
@marquiz: #1885 failed to apply on top of branch "release-0.16":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Very low risk for backporting, even if it brings new functionality, modifying the source |
Follow-up to #1878
To avoid port conflicts while running in hostNetwork mode we have to make the health ports configurable.
Tested via