Skip to content
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

Support health and liveness probes #297

Closed
j-vizcaino opened this issue Jan 16, 2019 · 10 comments
Closed

Support health and liveness probes #297

j-vizcaino opened this issue Jan 16, 2019 · 10 comments
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.

Comments

@j-vizcaino
Copy link
Contributor

I'm adding a liveness probe to a manager built with controller-runtime.
The manager already leverages the HTTP service provided natively to serve Prometheus metrics.

I would like to add another endpoint /live to provide the liveness of the application, on the same HTTP server that is used for metrics.
There does not seem to be a way to do this today because the http mux is created internally and attached to the HTTP server.

A way to circumvent this is to basically copy/paste the http server logic into a package of my own and add the extra handler but it feels sad that there is no way to reuse the existing code.

@DirectXMan12
Copy link
Contributor

we should have a general liveness hook. I'm not sure we want to make this a general HTTP serving platform, but liveness support would definitely be useful.

/kind feature
/priority important-longterm

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Jan 16, 2019
@j-vizcaino
Copy link
Contributor Author

Agreed, having a standard way for serving a liveness hook would be nice.
At the very least, it would be useful to be able to provide the HTTP server somehow as that would let the user tweak and reuse that component elsewhere.

@DirectXMan12
Copy link
Contributor

/good-first-issue

@k8s-ci-robot
Copy link
Contributor

@DirectXMan12:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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/test-infra repository.

@k8s-ci-robot k8s-ci-robot added good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Mar 6, 2019
@DirectXMan12 DirectXMan12 changed the title Adding custom endpoints to HTTP server Support health and liveness probes Apr 8, 2019
@GrigoriyMikhalkin
Copy link
Contributor

Hi, i would like to try to implement this.

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Aug 4, 2019
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Sep 3, 2019
@DirectXMan12
Copy link
Contributor

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. labels Sep 3, 2019
@estroz
Copy link
Contributor

estroz commented Nov 11, 2019

@DirectXMan12 has this been fully implemented in #419 or is there more to do?

@DirectXMan12
Copy link
Contributor

DirectXMan12 commented Dec 3, 2019

I think it's fully implemented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Development

No branches or pull requests

6 participants