Stuck at Tomcat 8.5.15 for AppEngine Flex?

[nealeu]

Hi (I'll take a guess at Mike),

Readme says that this is an archived project. Could this be updated to say why or at least direct people as to what they should be doing instead of using FROM gcr.io/google-appengine/tomcat:8 in their Dockerfile?

As far as I can tell from looking at docs (I just wrote Docks, thanks to hands reprogrammed to type "Docker") for App Engine Standard and Flexible, there's no deprecation, yet the Tomcat image is now quite outdated.

Thanks.

(edit) Additionally, the out of the box experience of adopting AppEngine is that numerous vulnerabilities show up in the GCR scan. Those don't currently relate to Tomcat because the analysis is limited to the OS at the moment. However, lowering the attack surface of the breadth of GAE would be helpful, and a base OS refresh would also eliminate the scan alerts. (/edit)

[meltsufin]

Note that this repo has always been experimental, and a Tomcat runtime for App Engine Flex never officially launched. Of course, you're free to fork this repo and make any updates you like and then use it as a custom runtime for your application, but it's not being maintained by anyone at Google.

[nealeu]

Thanks Mike.
BTW. If there's too much to do and not enough people, I'd be quite interested to join the London office to help out :-) I'm particularly interested in what could be done to facilitate more compute efficient Java workloads. I'd love to bring the simplicity and optimisation of AppEngine Standard to custom image K8s deployments.

[meltsufin]

I'm no longer involved in the runtimes. So, I can't speak as to the reasons, but Google Cloud is always looking for strong engineers. I'm sure you can easily find how to apply. 😉