Thank you Miguel for the clarification. Currently the App Engine Flexible environment requires at least one instance <https://cloud.google.com/appengine/docs/flexible/python/flexible-for-standard-users#scaling_characteristics> to be active in a version in order for requests to be routed to it. Our engineering team is working very hard on a good "scale to zero" solution for the Flex environment. There is currently no ETA for its implementation.
In the meantime, there is a great article on Reducing Costs for App Engine Flex <https://medium.com/google-cloud/three-simple-steps-to-save-costs-when-prototyping-with-app-engine-flexible-environment-104fc6736495> that I recommend you read. The idea is the same, reduce instances, but for every deployed version and service. When you deploy a new version on your app, App Engine will keep the instances of older versions running. This will in turn increase costs for every deployed version and service. You should therefore ensure to delete all instances in all unused versions. --------------------------------------- Concerning health checks. Health check requests to your application will not affect performance or cost. A health check will not ask your application to do any work, and instead simply pings the instance and container running your application to ensure they are alive and well. -- 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/0337d53b-e93f-4890-a911-2e973ccacd43%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
