kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix stale info about Pod scheduling readiness 

This is now a stable part of the Pod API.
This commit is contained in:
Tim Bannister 2024-06-03 23:32:03 +01:00
parent 8633dda5d7
commit 2e638c35c4
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
content/en/docs/concepts/workloads/pods/pod-lifecycle.md
View File

@ -43,6 +43,10 @@ is [terminated](#pod-termination); if Kubernetes isn't able start the Pod on the
node (for example, if the node crashes before the Pod starts), then that particular Pod
never starts.
You can use [Pod Scheduling Readiness](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/)
to delay scheduling for a Pod until all its _scheduling gates_ are removed. For example,
you might want to define a set of Pods but only trigger scheduling once all the Pods
have been created.
### Pods and fault recovery {#pod-fault-recovery}
@ -370,13 +374,6 @@ after successful sandbox creation and network configuration by the runtime
plugin). For a Pod without init containers, the kubelet sets the `Initialized`
condition to `True` before sandbox creation and network configuration starts.
### Pod scheduling readiness {#pod-scheduling-readiness-gate}
{{< feature-state for_k8s_version="v1.26" state="alpha" >}}
See [Pod Scheduling Readiness](/docs/concepts/scheduling-eviction/pod-scheduling-readiness/)
for more information.
## Container probes
A _probe_ is a diagnostic performed periodically by the [kubelet](/docs/reference/command-line-tools-reference/kubelet/)