From 2e638c35c499653a12fa9dba2a39ab5769359263 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Mon, 3 Jun 2024 23:32:03 +0100 Subject: [PATCH] Fix stale info about Pod scheduling readiness This is now a stable part of the Pod API. --- .../en/docs/concepts/workloads/pods/pod-lifecycle.md | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md index d7818b39f0..3695e56951 100644 --- a/content/en/docs/concepts/workloads/pods/pod-lifecycle.md +++ b/content/en/docs/concepts/workloads/pods/pod-lifecycle.md @@ -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/)