Merge branch 'mek/single-node-install-table' into 'master'

Add single node installation table for 1000 users

See merge request gitlab-org/gitlab!30071

doc/administration/scaling/index.md

@@ -58,6 +58,12 @@ On different cloud vendors a best effort like for like can be used.
 From 1 to 1,000 users, a single-node [Omnibus](https://docs.gitlab.com/omnibus/) setup with frequent backups is adequate.
 Please refer to the [installation documentation](../../install/README.md) and [backup/restore documentation](https://docs.gitlab.com/omnibus/settings/backups.html#backup-and-restore-omnibus-gitlab-configuration).
 
+| Users | Configuration[^8]    | GCP type      | AWS type[^9] |
+|-------|----------------------|---------------|--------------|
+| 100   | 2 vCPU, 7.2GB Memory | n1-standard-2 | c5.2xlarge   |
+| 500   | 4 vCPU, 15GB Memory  | n1-standard-4 | m5.xlarge    |
+| 1000  | 8 vCPU, 30GB Memory  | n1-standard-8 | m5.2xlarge   |
+
 This solution is appropriate for many teams that have a single server at their disposal. With automatic backup of the GitLab repositories, configuration, and the database, this can be an optimal solution if you don't have strict availability requirements.
 
 You can also optionally configure GitLab to use an [external PostgreSQL service](../external_database.md) or an [external object storage service](../high_availability/object_storage.md) for added performance and reliability at a relatively low complexity cost.