Is there some way to force pod creation order on Kubernetes?
I have a scenario where Kubernetes are selecting a node pool with few resources and the first pod to be deployed consume a very small resource, but the next one consumes a lot of resources and the deployment fails.
So I was wondering if there is a way to instruct Kubernetes to deploy first the pod that is resource hog then the small ones