Geo: redirect /edit and /new routes to primary
This can act as a simpler proposal of https://gitlab.com/gitlab-org/gitlab-ee/issues/3764.
Instead of serving the UI to create or edit an issue/mr/whatever from the secondary, and then routing the POST/PUT to the primary, we would redirect the user to /new
or /edit
on the primary node. The POST/PUT would then automatically end up at the primary any way.
Advantages
- Since the user is on the primary upon submit, the result would also be shown from the primary node, so db replication lag to the secondary wouldn't be an issue.
Disadvantages
- Latency: when the user has a slow connection to the primary, it takes longer to load the page