Tim Bannister
Tim Bannister
Does this only happen with `kubectl`, or do the symptoms also show up when making a request using (eg) `curl`?
How I'd tackle this: - update https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced to mention that container failure can lead to forced Pod termination (for example: if the [restart policy](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#restart-policy) is `Never`) - also update https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced...
/triage accepted /sig network /priority backlog
https://github.com/kubernetes/kubernetes/pull/110191#issuecomment-1142294392 says: > From what I can find within the code, K8S has always assumed that a pod without a readiness probe stays in ready=true until it has fully terminated....
Extra credit: add a diagram somewhere (might be easier once https://github.com/kubernetes/website/pull/36675 has merged)
The overall idea here is to probe Pods for _readiness_, even during shutdown, and use that readiness information to drop backends out of Services more gracefully. Because unexpected failures can...
/transfer kubectl
/kind feature /sig cli
Changelog suggestion (edited) ```diff -When duplicated keys are registered on `matchLabelKeys`, the validation will fail with an explicit error. +Added validation for Pod `matchLabelKeys` duplicates. When any duplicated keys are...
Do we also validate PodTemplate?