Google has initiated the migration of its Server-side Google Tag Manager from Container Registry to Artifact Registry on Google Cloud Platform, implementing a seamless transition strategy for users.
The container image migration has been executed without URL modifications, ensuring existing deployments remain functional. The original Docker image URL continues to operate normally for server-side tagging deployments.
Impact on Different Services
Server-Side Tagging Applications
- No user action required
- Existing deployments continue to function normally
- Container image accessibility maintained
Cloud Run Functions
- Automatic migration to Artifact Registry
- Requires enabled Artifact Registry API
- Specifically applies to 1st Gen functions
While server-side tagging applications require no intervention, users operating other Container Registry-dependent services should consult Google's migration guide. The transition primarily affects organizations with custom container deployments or additional services utilizing Container Registry.
The migration preserves the container URL structure, allowing systems to continue pulling the container image from Google's repository without disruption. This approach ensures operational continuity for server-side tagging implementations while modernizing the underlying infrastructure.
