I got the cause and hence the resolution. The pods were not getting created because the scheduler was unable to fit the new deployment on the available minions. When I added few more minions by editing the corresponding auto-scaling group, it succeed.
On Wednesday, June 29, 2016 at 4:31:46 PM UTC+5:30, Manoj Khotele wrote: > > Hello, > > I am creating many deployments together using a bash script. > Few of the deployments would be in Unavailable state. The corresponding > pods would be in pending state. > > This is not the case, if I do the same one by one. > I can have all the deployments successfully, if I wait for previous > deployment to be available. > > Be assure that there is no dependency issue. > The k8s version I am using is v1.2.3. > > What's going wrong? > Is it expected that a new deployment should be created only after all > previous deployments are successfully created and those are available? > > Best Regards, > Manoj > -- You received this message because you are subscribed to the Google Groups "Containers at Google" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-containers. For more options, visit https://groups.google.com/d/optout.
