Google Cloud Container Registry: Avoiding Duplicate Image Bloat

Viewed 17

I noticed that every Google Cloud Function maintains its own image file in the Google Container Registry, even though all cloud functions share the exact same source code and are just specifying different code-entry points.

Is it possible to deploy different cloud functions, each with their own code entry-point, from just a single container hosted in the Container Registry?

The only way I see this happening right now is by using a single Cloud Function that first routes requests to the correct handler function in-code.

0 Answers
Related