Geo: Add a data flow diagram for secondary proxing
Problem to solve
Geo introduced the ability to transparently proxy write requests from a secondary site to the primary site. The secondary site is able to accelerate most read requests by serving them from it's local data stores.
This is a very useful enhancement to the Geo solution which greatly improves the use experience for our customers. However, we currently don't have an end-to-end picture how the data/requests flow through the different GitLab components at the Geo sites.
Proposal
Add a data flow diagram to compliment the Geo proxying for secondary sites instructions.
Other links/references
Edited by Catalin Irimie