Redesigning Kubelet Probes

[tssurya]

Enhancement Description

• One-line enhancement description (can be used as a release note): Redesign Kubelet Probes
• Kubernetes Enhancement Proposal: KEP-4559 Redesigning Kubelet probes #4558
• Discussion Link:
  - Add TCP/HTTP/network requests to the CRI API kubernetes#102613
  - Pod probes lead to blind SSRF from the node kubernetes#99425
  - Pod readiness probe cannot be directed at specific IP family kubernetes#101324
  - Sometime Liveness/Readiness Probes fail because of net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) kubernetes#89898
  - Kubelet TCP/HTTP probes: improve network resources utilization kubernetes#115143
• Primary contact (assignee): @tssurya @danwinship
• Responsible SIGs: sig-network
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): 1.32
  • Beta release target (x.y): 1.34
  • Stable release target (x.y): 1.36
• Alpha
  • KEP (k/enhancements) update PR(s): KEP-4559 Redesigning Kubelet probes #4558
  • 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.

/sig network

[tssurya]

/sig network

[tssurya]

/assign @tssurya

[danwinship]

/assign

[thockin]

I assume the goal is to alpha in 1.31?

[thockin]

@tssurya did you bring this up at a SIG meeting and I missed it? If not, might be good to raise awareness.

[thockin]

Is there any part of this we want in 1.31? Clock is ticking.

[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

[tssurya]

/remove-lifecycle stale

[tssurya]

@tssurya did you bring this up at a SIG meeting and I missed it? If not, might be good to raise awareness.

not yet, and no specific clocks/urgency I am targeting this for...
Having said that we are working with sig-auth where we gave a headsup to them for adding PSA to block the existing fields

[thockin]

Is any part of this shooting for 32?

[tssurya]

Is any part of this shooting for 32?

In the efforts of trying to get some reviews from sig-node... I'll try to go to one of the sig-node meetings to present this better