Launch Artifact Registry on Runway with Fairway in GKE
## DRI
@fforster
## Participants
* @fforster @s.abbasi @gsgl @jomartin1 @artemmikha @rmakram @mjhoad
## Context
The Module Service (Runway) team has committed to providing the infrastructure deployment tooling for the initial gitlab.com / GKE launch of Artifact Registry (AR). AR will launch first as a SaaS-based service and use the Runway deployment tooling (Fairway) to generate Helm charts, store them respectively, and funnel generated artifacts through Runway CI and deployment mechanisms to deploy to GKE on Google Cloud.
## Goals
1. Provide the underpinning infrastructure deployment tooling for AR to deploy in a self-service fashion, free of manual infra or database creation.
2. Provide all the requisite options for provisioning and configuring components via the Fairway chart generation tooling.
1. Packaged application to GKE
2. Provision of Cloud SQL database with automatic backups and verifications (migrations not in scope)
3. Provision of Redis / Memorystore capacity
4. Provision of object storage in GCP GCS
5. Provision of Private Service Connect
6. Provision of CDN resources (?)
## Dependencies & Stakeholders
These teams should be consulted and tagged for reviews for this project:
* Artifact Registry
* Database Operations
These teams should be informed about this project:
* Production Engineering - Fleet
* Delivery - Build & Operate, Release & Deploy
epic