Will the deployment cost be reduced by migrating to Artifact Registry with appengine standard?

Google Cloud Compute Infrastructure
1

We are considering migrating from Container Registry to Artifact Registry to reduce deployment costs.

Q1: Is it correct to understand that if we set the following routing in gcloud beta artifacts settings enable-upgrade-redirection, the cost will be higher than before?
Q2: Is there any way to make the entity of projectss/myprj/locations/asia/repositories/asia.gcr.io in the asia-northeast1 region?
Q3: Is it possible and recommended to use Artifact Registry with appengine standard?

I have a golang app hosted in asia-northeast1 region in appengine’s standard environment.
After the rate change in October 2022, we have to pay Cloud Storage fee every time we deploy to appengine.
The reason for the cost is due to network bandwidth where appengine is hosted in multiple regions and container images are sent to multiple regions when deploying.
I would like to remove the multi-region setting, but appengine does not allow me to change the multi-region setting of the project.
In GCP, if I migrate from Container Registry to Artifact Registry and keep container’s image in a single region, I can free the cost of deploy.

https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr

However, according to this migration guide,
“A gcr.io repository can only be created in the same multi-region as the Container Registry host.”

A dry-run of gcloud beta artifacts settings enable-upgrade-redirection resulted in the following

$ gcloud beta artifacts settings enable-upgrade-redirection --project=myprj --dry-run
Performing redirection enablement checks...

Performing redirection enablement checks... Redirection enablement report

Container Registry Host Location Artifact Registry Repository
gcr.io us projects/myprj/locations/us/repositories/gcr.io
us.gcr.io us projects/myprj/locations/us/repositories/us.gcr.io
asia.gcr.io asia projects/myprj/locations/asia/repositories/asia.gcr.io
eu.gcr.io europe projects/myprj/locations/europe/repositories/eu.gcr.io

It looks like this will only make the deploy cost more expensive than before, even if we migrate to Artifact Registry.

2

Hi @tkenta ,

Welcome to Google Cloud Community!

Q1: Enabling the upgrade redirection feature in Artifact Registry can result in increased deployment costs, as it redirects all requests to the new repository, including requests from regions outside of the specified region.

Q2: It is not possible to create a repository in a specific region in Artifact Registry, as the repository’s region is determined by the Artifact Registry location resource associated with the project.

Q3: It is possible and recommended to use Artifact Registry with App Engine standard to reduce the deployment costs associated with multi-region container image storage. You can configure your App Engine application to use a specific Artifact Registry repository in the same region as the App Engine service by specifying the repository’s URL in the app.yaml file or using the gcloud app deploy command with the --image-url flag.

Thanks

3

Thank you for answering.

But --image-url works only in appengine’s flexible environment.
https://cloud.google.com/sdk/gcloud/reference/app/deploy

Therefore, it seems that the Artifact Registry cannot be used in the standard environment of appengine.

When I deploy with this command,

“gcloud app deploy app.yaml --project=myprj”

Fees are charged for the following items.

  • Networking Traffic Egress GCP Replication within Asia
  • Networking Traffic Egress GCP Multi-region within Asia

We are looking into ways to reduce this cost.
Any advice would be appreciated.
・Can we reduce costs by not using the default bucket with the bucket option?
https://cloud.google.com/sdk/gcloud/reference/app/deploy