Exactly, it would be nice to separate the reverse proxy that provides access to some other service from the app.
Another use case is adding a second fluentd container so we could send log events to our own monitoring system and not just stackdriver. We could either create a new container with another fluentd or customize the already deployed google-fluentd container. On Friday, March 10, 2017 at 7:28:01 PM UTC+2, Zachary Fewtrell wrote: > > Hi Mikko, > Currently App Engine flex does not support definition of sidecars or > multiple containers. Can you go into more detail about your use case? Are > you hoping to use a standard reverse proxy as a separate container so you > can have clean separation of the reverse proxy from the application server? > > Regards, > Zach Fewtrell > > On Thursday, March 9, 2017 at 6:13:25 AM UTC-8, Mikko Sivulainen wrote: >> >> Hi, >> >> We've been playing around with custom runtime images for flexible app >> engine. >> It would be very helpful if we could just build custom containers and >> have them run as sidecars with the standard jetty container. Now we have to >> edit the app container to include stuff we need and modify entrypoint so >> that they get launched. I guess there is currently no way of defining extra >> sidecars when deploying? >> >> -- 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/da1d2eb4-52c1-4f69-93e6-8c3b3f73c19c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
