Add HEAD Request Probes

[tobiasgiese]

Enhancement Description

• One-line enhancement description (can be used as a release note): HEAD Request Probes (see https://github.com/kubernetes/kubernetes/issues/49937)
• Kubernetes Enhancement Proposal: TBD
• Discussion Link: https://kubernetes.slack.com/archives/C0BP8PW9G/p1684163811402519
• Primary contact (assignee): @tobiasgiese
• Responsible SIGs: /sig node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): v1.28
  • Beta release target (x.y): v1.29
  • Stable release target (x.y): v1.30
• [ ] Alpha
  • [ ] KEP (k/enhancements) update PR(s):
  • https://github.com/kubernetes/enhancements/pull/4012
  • [ ] Code (k/k) update PR(s):
  • [ ] Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

_{Tobias Giese tobias.giese@mercedes-benz.com, Mercedes-Benz Tech Innovation GmbH, legal info/Impressum}

[tobiasgiese]

/sig node

[tobiasgiese]

/assign

[leonardpahlke]

cc

[SergeyKanzhelev]

I'm still not convinced this work worth the added API/complexity. Adding to the milestone to have it on the radar since it is being worked on

/milestone v1.28

[Jeeppler]

I'm still not convinced this work worth the added API/complexity. Adding to the milestone to have it on the radar since it is being worked on

May, I ask why you are not convinced?

From my point of view as a user and consumer, not having the head liveness probe is one of the most counterintuitive API design choices of Kubernetes. From my understanding of the HTTP protocol, using HTTP HEAD to check if a service is alive is the obvious and best choice.

[pohly]

May, I ask why you are not convinced?

Better discuss that in the KEP PR:

• https://github.com/kubernetes/enhancements/pull/4012#discussion_r1207414906
• https://github.com/kubernetes/enhancements/pull/4012#discussion_r1207342809

[salehsedghpour]

Hello 👋 1.30 Enhancements Lead here,

I'm closing milestone 1.28 now, If you wish to progress this enhancement in v1.30, please follow the instructions here to opt in the enhancement and make sure the lead-opted-in label is set so it can get added to the tracking board and finally add /milestone v1.30. Thanks!

/milestone clear

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Jeeppler]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Jeeppler]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[colearendt]

/remove-lifecycle rotten