Open tobiasgiese opened 1 year ago
/sig node
/assign
cc
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
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.
May, I ask why you are not convinced?
Better discuss that in the KEP PR:
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
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Enhancement Description
k/enhancements
) update PR(s):k/k
) update PR(s):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