I have an on-prem Kubernetes cluster and recently it required a physical restart of all the worker nodes (run three worker nodes). When the pods came back up, I noticed all the pods scheduled on a single physical worker node instead of being spread out evenly across the three worker nodes. I am assuming the other two worker nodes took longer to come back online from the restart and Kubernetes just scheduled all our applications on the only worker node up.
Is there a way in the deployment yaml to specify that all deployment replicas should be spread out eventually across all worker nodes? I.E. prevent Kubernetes from starting all pods on a single worker node?