Set up new GCP infrastructure for CE & EE Review Apps
In light of implementing Review Apps for CE and EE, we need to setup a separate GCP instance so we can monitor and control the cost. Since Review Apps will be spun up for every merge request, we are anticipating a spike in usage and also billing.
- Issue: gitlab-org/release/tasks#255 (comment 81234195)
- Working document: https://docs.google.com/document/d/1XGMHWm-7vRTVE4E-a8LDQSDXK4HPfAmsXakghMKWeak/edit
As discussed with Art and Chase earlier, it is possible to share the existing billing account as long as its easy to separate the load of this initiative from the rest of our GCP usage.
Also as discussed with Kathy earlier, the Security team needs to be looped in to review and vet this new environment.
Requirements
- A separate GCP instance with its own container registry. This allows us a single point of control for cost/usage.
- This should be in its own separate project space and isolated from the rest of the GCP infrastructure.
- This can be structured to the same billing account with what we have.
- Main users will be the Release and Quality team as we continue to build out CI & Test automation flows.
- Shared access for Infrastructure team to monitor cost model and Security team for security.
- A notification mechanism to keep Finance team in the loop if we are anticipating a spike in usage which affects our bill.
Users
The users that need access to configure this new instance.
- @marin
- @rymai
- @rspeicher
- @jameslopez
- @markglenfletcher
- @meks
- @glopezfernandez
- @andrewn
- TBD & security team?
- All Production Engineers
/cc @artNasser @wwright