This page contains information related to upcoming products, features, and functionality.
It is important to note that the information presented is for informational purposes only.
Please do not rely on this information for purchasing or planning purposes.
The development, release, and timing of any products, features, or functionality may be subject to change or delay and remain at the
sole discretion of GitLab Inc.
| Status | Authors | Coach | DRIs | Owning Stage | Created |
|---|---|---|---|---|---|
| proposed | devops data stores | - |
Cells ADR 002: One GCP Project per Cell
Context
We discussed whether we should have each Cell in its own GCP project or have all Cells in one GCP project in this issue.
Decision
It was unanimously decided that we should have one GCP project per Cell. Doing so gives us better isolation between Cells, compatibility with current Dedicated tooling, less likelihood of running into per-project quotas, and easier change rollouts (we can roll out changes per-project).
There is no limit to how many projects we can create.
Consequences
This decision means that inter-Cell networking becomes slightly less straightforward. However, it is not clear at this point if it’s actually needed, and it’s being discussed
Alternatives
The choices discussed above are really the only two possible outcomes.