Deploying a custom sidecar container in flexible

82 views
Skip to first unread message

Mikko Sivulainen

unread,
Mar 9, 2017, 9:13:25 AM3/9/17
to Google App Engine
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?

Zachary Fewtrell

unread,
Mar 10, 2017, 12:28:01 PM3/10/17
to Google App Engine
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

Mikko Sivulainen

unread,
Mar 10, 2017, 1:53:16 PM3/10/17
to Google App Engine


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.

Alex (Cloud Platform Support)

unread,
Mar 14, 2017, 1:33:47 PM3/14/17
to google-a...@googlegroups.com

Hi Mikko,


I see that you have appropriately opened a feature request on this Issue Tracker thread (Allow deployment of additional sidecar containers #36113449) and would like to confirm you that it has been submitted to the backline team. To you and to anyone reading this post in the future, feel free to follow any updates on the request via the previously provided Issue Tracker thread.


Cheers,

Alex

Mikko Sivulainen

unread,
Mar 14, 2017, 1:51:09 PM3/14/17
to Google App Engine
Thanks,

Just to clarify, the link you use is internal to Google. Public issue tracker address is https://issuetracker.google.com/issues/36113449

Alex (Cloud Platform Support)

unread,
Mar 15, 2017, 11:10:26 AM3/15/17
to Google App Engine
Thanks for checking that out, the link to the thread is now updated.
Reply all
Reply to author
Forward
0 new messages