Migrate to Stanford GitLab's New Container Registry By March 27

Stanford GitLab (code.stanford.edu) is moving to a new, improved Container Registry. If you use the Stanford Container Registry (not a third-party registry provider), you must manually migrate your container images by March 27, 2026, to ensure your automated continuous integration and delivery (CI/CD) jobs continue to work as expected. No data will be automatically migrated.

How to verify if you are impacted

• Not impacted: If you use an external registry (e.g., Google Container Registry/Artifact Registry, Amazon ECR, Azure ACR, Docker Hub or another third-party provider), you are not affected by this transition.
• Impacted: If you only use the Stanford Container Registry (scr.stanford.edu), please follow the actions required below to migrate your container images to cr.stanford.edu by March 27, 2026.

Action required for those impacted

• Those with images hosted on the Stanford Container Registry (scr.stanford.edu) must self-migrate to the new cr.stanford.edu endpoint before the March 27, 2026, cut-over.
• To begin your migration, follow the Instructions in the Migration Guide.
• Verify that your images have been successfully moved to the new registry.
• You can start using the new registry immediately to ensure your workflows continue to function without interruption after the cut-over to the new registry service.
• Old data is not being deleted; it will remain on the legacy system until you move it.

This update is part of our effort to provide an improved service to the Stanford community, with better integration, enhanced performance, and a modernized storage backend. The change has also been announced via a broadcast message on https://code.stanford.edu.

Get help

• Report any migration issues to the Stanford GitLab service team.
• For general questions about Stanford GitLab, please submit a Help request.