Introduce hot disable of probes

[Chaunceyctx]

Enhancement Description

• One-line enhancement description (can be used as a release note):
  Introduce hot disable of probes, which can be suspended by user manually. from Allow hot disabling of liveness probes kubernetes#57187
• Kubernetes Enhancement Proposal: WIP
• Discussion Link: https://docs.google.com/document/d/1qdwAXvvyHINf4h_taC7EnDNjsyt-u9wwzJt1oJf97Cs/edit?tab=t.0
• Primary contact (assignee): @Chaunceyctx
• Responsible SIGs: sig-node
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y):
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s):
  • 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 node

[Chaunceyctx]

/ping gently @tallclair
If we allow users to modify the configuration items of container probes, is it still necessary to propose a KEP to track it?

pr draft: kubernetes/kubernetes#129541 more e2e test units to prove)

[Chaunceyctx]

/ping gently @tallclair If we allow users to modify the configuration items of container probes, is it still necessary to propose a KEP to track it?

pr draft: kubernetes/kubernetes#129541 more e2e test units to prove)

After consideration, since users who modify the configuration would definitely want to know if these configurations have taken effect, there should be a status field to record whether these configurations are in effect :)

Perhaps we indeed need to add some fields?