Geo: QA CI runner registration with secondary sites when Unified URL and proxying is enabled

Problem to solve

Since the introduction of Unified URL and proxying it is now possible for secondary sites to register CI runners. This is a very useful capability for our customers.

It will be good to formally announce support for this but before we do we need to ensure all supported use cases error free.

We are aware of limitations in relations to using CI runners with separate secondary URLs and have documented it here

Proposal

Test the following configurations and scenarios:

• Setup a Geo deployment. It will be good to test 1k and 3K to ensure everything works as expected in a HA architecture.
• Setup Unified URL and proxying
• Register CI runners on both the secondary and primary sites
• Test fail over scenarios to confirm correct operation
• Check large clone operations work correctly
• Check logic with both native Geo object storage replication and provider managed replication.
• Check dependency proxy logic. It is possible this does not work correctly. We want to identify if this is a gap and call it out when announcing the feature.

Acceptance criteria

• Runners clone from the closest secondary site.
• Clone requests to secondary site from CI runners are proxied to primary site when the secondary site is not up to date.
• Check all accelerate data types are served from the secondary site
• Ensure all authentication and authorization flows require by the CI runners complete successfully
  • Validate with locally stored passwords
  • Validate with LDAP/SSO configuration
• Ensure CI runner behaviour after fail-over event
  • Runners should continue to work with new primary site
• Large clone operations are successful