Add a limit for the allowed number extra pages deployments
Problem
Pages Multiple Deployments feature will enable users to create, as the name suggests, multiple active deployments for the same Pages site at the same time. This could create pressure on the Storage and in the internal API that servers the available pages sites for the requested domain/namespace.
Proposed solution
Add limits of the number of extra active Pages deployments (deployments not marked to be deleted and with a not blank path_prefix
) versions a namespace can create. The limit will be in the namespace level to mitigate the pressure in the internal API, since it servers the available pages sites for the requested domain/namespace.
On Saas
Initial limits, for the first iteration:
- Silver GitLab Premium 100
- Gold GitLab Ultimate 500
When the limit is reached, we should show a message letting the user now the limit was reached.
On Self-managed
We're also introducing a limit on self-managed to avoid problems with the pages internal API. 1000
Possible future iterations
- To make these limits less restrictive, we might not count the projects using unique domain, since they don't impact on the internal api response.
Steps to Finalize
-
Matt and @kassio to meet on 2024-02-22 to discuss paths forward outside of Project storage. -
Work with @joshlambert to ensure this feature complies with standards around infrastructure costs. -
Meeting set up for 2024-02-29
-
-
Work with @SeanHall to verify the pricing strategy for this feature and cross-check the competition. -
Meeting sest up for for 2024-03-05
-