dualfroz
a8bc9d02d5
createOrGetDeployment decided whether to wait for readiness from the Status.AvailableReplicas of the copy it read before ScaleDeployment, the same pattern the container manager had. On the scale-from-zero path that copy can still count the pod the idle reaper is tearing down, so WaitForDeployment, and with it the ObservedGeneration gate, was skipped entirely. Track whether we issued the scale-up and always wait in that case. The test covers both the pre-scale read and a status the controller has not caught up with yet.