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 httpHead for pod livenessProbe #49937

Closed
SEJeff opened this Issue Aug 1, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@SEJeff
Contributor

SEJeff commented Aug 1, 2017

/kind feature

What happened:
The docs for http liveness probes only reference httpGet, but a http HEAD request is better for healthchecks as no data is returned so it is lighter weight.

What you expected to happen:
I would expect a httpHead directive to exist. It would perform a request such as:

HEAD / HTTP/1.1

vs httpGet, which does something like:

GET / HTTP/1.1

How to reproduce it (as minimally and precisely as possible):

Create a livenessProbe and be 😞 that HEAD requests aren't available.

@SEJeff

This comment has been minimized.

Show comment
Hide comment
@SEJeff

SEJeff Aug 1, 2017

Contributor

/sig node

Contributor

SEJeff commented Aug 1, 2017

/sig node

@spunon

This comment has been minimized.

Show comment
Hide comment
@spunon

spunon Dec 19, 2017

Any movement on this? This would be extremely helpful.

spunon commented Dec 19, 2017

Any movement on this? This would be extremely helpful.

@SEJeff

This comment has been minimized.

Show comment
Hide comment
@SEJeff

SEJeff Dec 21, 2017

Contributor

Seems like a super useful feature for lightweight monitoring.

Contributor

SEJeff commented Dec 21, 2017

Seems like a super useful feature for lightweight monitoring.

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Mar 21, 2018

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

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

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Apr 20, 2018

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
/remove-lifecycle stale

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
/remove-lifecycle stale

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot May 20, 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment