-
Notifications
You must be signed in to change notification settings - Fork 104
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Introducing http-endpoint #95
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
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.
So this means we start two servers. One for the metrics and the other for healthz? Is it possible to do it in one server?
I am trying to understand why
metricsManager.RegisterToServer(mux, *metricsPath)
will not work.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.
And could you remind me why do we need the http-endpoint?
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 to be consistent with all other sidecars - every sidecar will have
http-endpoint
as the flag to specify where the its HTTP server should run (e.g. kubernetes-csi/external-provisioner#537). This also eliminates the limitation that health check and metrics must run on different ports.This keeps the original behavior of being able to specify different ports for health check and metrics, to maintain backward compatibility. If
metrics-address
isn't set explicitly, we do exactly as you described.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 see, thanks! I think we might want to remove this on the next major release. But this looks good to me.
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.
So to make it as simple to use as possible, can we do this ?
Combine the metrics port and healthz port together. I don't see the benefit of separate them apart. So the change can just be: if http-endpoint is set, we just use that endpoint to expose metrics and healthz and ignore whatever the healthz and metrics_address setting. Otherwise keep the current behavior.
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.
The tricky thing is currently
http-endpoint
has a default value (to inherit the behavior ofhealth-port
), and unfortunately the golang flag package doesn't have the ability to distinguish between something that's set vs unset.