I'm adding some wording to our hardware requirements to explain that needs vary
by workload. I also included some examples of factors that may influence the
workload.

* Use `GiB memory` to describe memory needs.
* Add local storage recommendation for monitoring node.
* Better align CPU/Memory to match common cloud provider instnace types.
* Update requirements based on the new 10k user standard.

- Make sure we have type defined in the frontmatter
- Add troubleshooting sections where absent
- Meaningful intros where absent

Marcel Amirault authored 5 years ago and Achilleas Pipinellis committed 5 years ago

Remove unneeded trailing whitespace in lines in
/development /ci /api and /administration docs.

Adding a note to the 10k reference architecturre that the resource recommendations are per node

Aric Buerer authored 5 years ago and Achilleas Pipinellis committed 5 years ago

Updating documentation to include
Prometheus Service Discovery. Added
monitoring node documentaiton as
well as documentation for the
individual service nodes.

The 10,000 user reference architecture work is ongoing. However, we have
done some preliminary investigation and testing and have an idea of
what we think the environment might look like. In the interest of
transparency, efficiency and iteration, let's get this out there.

Add opening text that was previously on https://about.gitlab.com/high-availability
and add a note that active/passive is compatible but not supported.

This reverts commit 3e991230.

# Conflicts:
#	app/models/project.rb