## Context **:warning: The deployment model for new modular services is under active discussion. At the time of writing, the current proposal is the [Infrastructure Module Rig (IMR)](https://docs.google.com/document/d/1Wsgzx6Mk7aJgWN6fQYpprAAwgtMsns5pPXR-b8oeRGY/edit?tab=t.0#heading=h.l1sbpajy0wbl). To decouple AR's infrastructure requirements from the model decision, we compiled a [concrete list of requirements and recommendations](https://docs.google.com/document/d/1GApsHWd3XaQ0Z40Dk7J_pM9sWqDDJlbD9tQuBiebHLI/edit). Please see this document for relevant context.** [Artifact Registry](https://gitlab.com/groups/gitlab-org/-/work_items/19844) is a new satellite service to be deployed on Runway GKE, providing organization-level unified artifact management. It will offer a superset of the functionality currently provided by Container Registry, Package Registry and Virtual Registry. This epic tracks the provisioning of all infrastructure dependencies required for the service on GitLab.com. It covers the conversation, decision-making, and provisioning across all required components. The Artifact Registry is currently on track for Q2 delivery and has already been onboarded to Runway GKE on GitLab.com. ## References - [Artifact Registry epic](https://gitlab.com/groups/gitlab-org/-/work_items/19844) - [Runway x Artifact Registry sync](https://docs.google.com/document/d/19it-1KtovN6y7yD9Rxo-IB9cRNDtZWLZXLglQLzmkp8/edit)