Hi Yannick, Yes I do. These specific instances need to be able to find one another in order to form a cluster. Was hoping this was possible now with App Engine Flex instead of going lower into the stack using Container Engine + Kubernetes API.
Op maandag 10 juli 2017 17:40:37 UTC+2 schreef Yannick (Cloud Platform Support): > > Hello Dirk, > > I don't believe there is a straightforward way to achieve what you're > trying to do with App Engine as this is not the intended use case. Is there > a specific reason you want to manually manage App Engine instances instead > of using a Container Engine <https://cloud.google.com/container-engine/> > cluster? > > On Sunday, July 9, 2017 at 3:06:09 AM UTC-4, Dirk Louwers wrote: >> >> Hi, >> >> I am currently trying to form a cluster with multiple GAE Flex instances. >> Therefore I expose the clustering port in the app.yml configuration. On >> instance start, an instance needs to be able to find it's peer instances in >> order to join the cluster. What is the best way to do this? >> >> I have tried using Google Cloud Metadata instance data, but this only >> tells me something about the instance itself. Is there a way to achieve >> this using Google Cloud Metadata or would you recommend using something >> like Consul or etcd et al.? >> >> Kind regards, >> >> Dirk Louwers >> > -- You received this message because you are subscribed to the Google Groups "Google App Engine" 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-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1803985e-c7cb-4f83-af88-eddd81826cad%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
