Google Cloud Emails

I have a web site with a list of books that I have read that is generated dynamically from a database. So probably once every 3 months I get some email like this from Google Cloud that makes almost no sense at all to me. This one is especially egregious. I have no idea what they are talking about.

Hello Nels, We’re writing to inform you about an important change that will impact your App Engine app. The older App Engine projects could be using Google Container Registry to store container images created from the deployed source code. Google Container Registry is being discontinued and will be replaced by Artifact Registry. This means if you have content in Google Container Registry, you need to follow the instructions below to allow App Engine to automatically migrate your deployment flows. We’ve provided additional information below to guide you through this change. What you need to know When deploying App Engine, Cloud Build transforms source code into container images which may be stored in Google Container Registry. Artifact Registry is the next-generation service for storing container images, offering improved regionalized storage and security features. Going forward, Artifact Registry will be the container repository used by App Engine. After a successful App Engine application deployment: The App Engine standard environment doesn’t require pulling from the container repository The App Engine flexible environment pulls from the container repository on each instance startup Upcoming changes: Starting March 5, 2025: New deployments will start using Artifact Registry instead of Google Container Registry for storing application images. After March 18, 2025: Google Container Registry will begin shut down, preventing App Engine flexible environment instances from starting. What you need to do If your project already uses Artifact Registry for gcr.io urls, either because you have run the automated migration tooling, or because it was created after May 2024, you can ignore the following instructions for that project. For projects which are not yet migrated you will need to follow these steps to enable App Engine to automatically migrate your deployment flows. App Engine standard environment users: For standard deployments to work correctly with Artifact Registry: The service account associated with deployments (typically this will be the App Engine default service account, project-id@appspot.gserviceaccount.com, or your custom service account) command should have a role that grants the explicit Artifact Registry permission artifactregistry.repositories.uploadArtifacts (for write). You can find this information by viewing the roles of the service account. New deployments will be able to use Artifact Registry, if any of the following roles are present in the service account associated with deployments: Editor role Pre-defined Artifact Registry role with write access (like Artifact Registry Writer). Custom role that grants artifactregistry.repositories.uploadArtifacts permission. It can be verified from the Console or through the gcloud iam roles describe command. If none of these roles are present, grant the Artifact Registry Writer role (roles/artifactregistry.writer) to your deploying service account. Potential Impact: If the preceding steps aren't completed before the Google Container Registry shuts down, you won't be able to deploy new versions of your App Engine standard application. Existing App Engine standard applications will continue to run. App Engine flexible environment users: For flexible deployments to Artifact Registry to work correctly: The service account associated with deployments (typically, this will be the App Engine default service account, project-id@appspot.gserviceaccount.com, or your custom service account) should have a role that grants the explicit Artifact Registry permissions: artifactregistry.repositories.downloadArtifacts (for read) and artifactregistry.repositories.uploadArtifacts (for write). You can find this information by viewing the roles of the service account. New deployments will go to the Artifact Registry if any of the following roles are present in the service account associated with deployments: Editor role Pre-defined Artifact Registry role with read and write access (like Artifact Registry Writer). Custom role that grants artifactregistry.repositories.downloadArtifacts and artifactregistry.repositories.uploadArtifacts permissions. These can be verified from the Console or through the gcloud iam roles describe command. If none of these roles are present, grant the Artifact Registry Repository Administrator role (roles/artifactregistry.repoAdmin) to your deploying service account. You can migrate manually built container images to Artifact Registry only by running the automated migration utility for your project. Potential Impact: If the preceding actions are not completed before the Google Container Registry shutdown, deploying App Engine flexible applications, scaling instances, and restarting instances will fail. We’re here to help If you have any questions or require assistance, please contact Google Cloud Support. Thanks for choosing App Engine.

— The Google Cloud Team