After updating a permitting portal Deployment image, a developer needs a CLI wait that blocks until the new ReplicaSet is progressing successfully. Which command is the right wait signal?
Select an answer to reveal the explanation.
Short Explanation
You don’t guess whether the movers finished—you stand at the door until they say “done.” kubectl rollout status watches the Deployment until the new ReplicaSet is healthy (or the progress deadline fails), so it’s the natural CLI wait after an image bump.
Full Explanation
kubectl rollout status tracks Deployment progress and exits when the rollout completes successfully or when it detects a failure such as ProgressDeadlineExceeded. It is the standard developer wait after applying a template change. Deleting the Deployment, scaling to zero, or writing an arbitrary annotation does not provide that progress signal and can disrupt availability.