There's not really a way to express that dependency. You can make the second container wait in a wrapper script, or just let it crash and get restarted until it can successfully start.
/MR On Fri, Sep 1, 2017, 16:32 Yong Zhang <hiscal2...@gmail.com> wrote: > Hi, all > > I have one pod with two containers e.g. A and B, > A should start after B because it relies on service B. > > I can't find any solution to make container A delay startup, is there any > workaround or best practices on Kubernetes for this scenario? Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
