Geo: Disabling proxying instruction do not disable SSH proxying
Problem to solve
Following the documentation to disable proxying does not disable SSH proxying. Relevant sections:
Applying both or either of these settings does not stop proxying of SSH required to the primary when the relevant conditions for proxying are met.
The content in these sections is misleads the reading into believing all proxying is stopped when the setting is applied.
Further details
This is possibly a result of changing the SSH proxying workflow to go through the GitLab shell instead of through Puma and Workhorse.
- Geo: Proxy Git fetch/clone over SSH via Gitlab Shell
- Geo: Fix timeouts when pushing via SSH to secondary
Proposal
We should start by updating the documentation to reflect the true up-to-date behaviour when the changes described in the sections are applied including the title of the sections.
If there is an alternative way to disable SSH proxying, we should highlight this.
Direct users to upvote or add use cases for read-only sites where necessary.
Who can address the issue
Geo team