In Kubernetes, conditions are designed to be persistent once initialized, transitioning its status between True, False, and Unknown (https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Condition). This allows automation via querying condition states, e.g. kubectl wait --for=condition=Suspended=False.
Conditions should also include a lastTransitionTime timestamp. Transitioning a condition to False preserves the exact timestamp of when the Sandbox successfully resumed. Removing the condition erases this history.
In Kubernetes, conditions are designed to be persistent once initialized, transitioning its status between True, False, and Unknown (https://pkg.go.dev/k8s.io/apimachinery/pkg/apis/meta/v1#Condition). This allows automation via querying condition states, e.g. kubectl wait --for=condition=Suspended=False.
Conditions should also include a lastTransitionTime timestamp. Transitioning a condition to False preserves the exact timestamp of when the Sandbox successfully resumed. Removing the condition erases this history.