Remove per_repository election strategy

For guidance on the overall deprecations, removals and breaking changes workflow, please visit https://about.gitlab.com/handbook/product/gitlab-the-product/#breaking-changes-deprecations-and-removing-features

Deprecation Summary

Gitaly no longer supports the per_repository election strategy, and therefore the configuration option should be removed. As clarified in this comment, the setting is currently ignored as input. In addition, removal of the election strategy will not cause a breaking change as the setting is completely ignored.

Breaking Change

As documented here, this is not a breaking change as the setting is ignored.

Affected Topology

This will impact all self-hosted installations.

Affected Tier

All tiers are impacted.

Checklist

• @mention your stage's stable counterparts on this issue. For example, Customer Support, Customer Success (Technical Account Manager), Product Marketing Manager.

  • To see who the stable counterparts are for a product team visit product categories
    • If there is no stable counterpart listed for Sales/CS please mention @timtams
    • If there is no stable counterpart listed for Support please @mention @gitlab-com/support/managers
    • If there is no stable counterpart listed for Marketing please mention @cfoster3

• @mention your GPM so that they are aware of planned deprecations. The goal is to have reviews happen at least two releases before the final removal of the feature or introduction of a breaking change.

Deprecation Milestone

We are announcing this deprecation in %14.8.

Planned Removal Milestone

As this is not a breaking change, we have confirmed we can remove the feature in %14.9 if we desire.

Links

Gitaly Issue: gitaly#3611 (closed)