From f4285d806dafe739c551d9bd42b824c8c0bbb0a4 Mon Sep 17 00:00:00 2001 From: Antoni Basista Date: Wed, 17 Jun 2026 12:49:22 +0000 Subject: [PATCH] Rename PodGroupScheduled condition to PodGroupInitiallyScheduled Kubernetes-commit: 0d59683459ab25f1430b0740989ca63935bdaa47 --- applyconfigurations/scheduling/v1alpha3/podgroupstatus.go | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/applyconfigurations/scheduling/v1alpha3/podgroupstatus.go b/applyconfigurations/scheduling/v1alpha3/podgroupstatus.go index d0b9d9943..aaa9c3879 100644 --- a/applyconfigurations/scheduling/v1alpha3/podgroupstatus.go +++ b/applyconfigurations/scheduling/v1alpha3/podgroupstatus.go @@ -30,11 +30,13 @@ type PodGroupStatusApplyConfiguration struct { // Conditions represent the latest observations of the PodGroup's state. // // Known condition types: - // - "PodGroupScheduled": Indicates whether the scheduling requirement has been satisfied. + // - "PodGroupInitiallyScheduled": Indicates whether the scheduling requirement has been satisfied. + // Once this condition transitions to True, it serves as a terminal state and will never revert to False, + // even if pods are subsequently evicted and group constraints are no longer met. // - "DisruptionTarget": Indicates whether the PodGroup is about to be terminated // due to disruption such as preemption. // - // Known reasons for the PodGroupScheduled condition: + // Known reasons for the PodGroupInitiallyScheduled condition: // - "Unschedulable": The PodGroup cannot be scheduled due to resource constraints, // affinity/anti-affinity rules, or insufficient capacity for the gang. // - "SchedulerError": The PodGroup cannot be scheduled due to some internal error