Merge pull request #3731 from jenkins-x/artifact_registry

docs: migrating to artifact registry

content/en/blog/news/2024-migrating-artifact-registry.md

@@ -0,0 +1,18 @@
+---
+title: "Improve your changelogs"
+date: 2024-05-06T00:00:00-00:00
+draft: false
+description: Google will shut down container registry  
+categories: [blog]
+keywords: [Jenkins X,Community,2024]
+slug: "migrating-artifact-registry"
+aliases: []
+author: Mårten Svantesson
+---
+
+## Migrate to Google Artifact Registry
+
+Google has announced that [container registry will be shut down some time after March 18, 2025](https://cloud.google.com/artifact-registry/docs/transition/transition-from-gcr). For GKE clusters created with version 1.12.0 or later of [terraform-google-jx](https://github.com/jenkins-x/terraform-google-jx) it's unlikely that anything needs to be done, but for older clusters you should upgrade your cluster while considering [our advice regarding migration from container registry to artifact registry](https://github.com/jenkins-x/terraform-google-jx#migration-from-container-to-artifact-registry).
+
+If you are using a Google Service Account to run terraform you need to add the role requirement roles/artifactregistry.admin. See our guide regarding [Google Service Account](https://jenkins-x.io/v3/admin/platforms/google/svc_acct/) for details.
+

content/en/v3/develop/faq/config/registries.md

@@ -8,6 +8,8 @@ weight: 154
 
 ## How do I use a custom container registry?
 
+What container registry is used by default depends on the which cloud provider you use. There are some things to consider when [migrating from container registry to artifact registry in Google GCP](https://github.com/jenkins-x/terraform-google-jx#migration-from-container-to-artifact-registry).
+
 To allow a pipeline to be able to push to a container registry you can add this secret...
 
 ```bash