Geo: [geo_object_storage_replication] Enable replicating uploads, LFS objects, and artifacts in Object Storage

Blocked on #33274 (closed)

What

Remove the :geo_object_storage_replication feature flag.

Owners

  • Team: @geo-team
  • Most appropriate slack channel to reach out to: #g_geo
  • Best individual to reach out to: @mkozono or @brodock

Expectations

### What are we expecting to happen?

Nothing, especially on GitLab.com since Geo isn't used there yet. On installations using Geo, the feature flag makes the setting sync_object_storage available to be set to true in Admin Area > Geo > Nodes.

What might happen if this goes wrong?

I can't think of something plausible for GitLab.com.

What can we monitor to detect problems with this?

Beta groups/projects

N/A

Roll Out Steps

(This doesn't apply so much to GitLab.com)

  • [-] Enable on staging
  • [-] Test on staging
  • Ensure that documentation has been updated => #14779 (closed)
  • [-] Enable on GitLab.com for individual groups/projects listed above and verify behaviour
  • [-] Coordinate a time to enable the flag with #production and #g_delivery on slack.
  • [-] Announce on the issue an estimated time this will be enabled on GitLab.com
  • [-] Enable on GitLab.com by running chatops command in #production
  • [-] Cross post chatops slack command to #support_gitlab-com and in your team channel
  • [-] Announce on the issue that the flag has been enabled
  • Remove feature flag and add changelog entry
  • [-] After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel
Edited by Michael Kozono