In general, Kubernetes does not support ordering dependencies. Applications should be resilient to transient failures (even crash-and-restart works), so it turn out to not really be needed, usually.
On Thu, Jan 11, 2018 at 11:56 AM, Kubernetes user discussion and Q&A <kubernetes-users@googlegroups.com> wrote: > Hello Users, > > I was wondering if someone can share some help here - > > I am looking to construct a manifest yaml that will contain all the > containers that need to be started by K8 in a particular order. I have a > list of dependencies (service graph is not acyclic) that I need to resolve > prior to produce a topological sort which will define the ordered list of > containers that will be fed in manifest. There are multiple versions of the > services in these containers and I need to enforce versioning as well in the > dependency graph. I am wondering if there is any existing infrastructure > that I can make use of to accomplish this process. Any help is appreciated. > > 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.
