[Feature flag] geo_pipeline_artifact_replication - Enable pipeline artifact replication with geo

What

Remove the :geo_pipeline_artifact_replication feature flag ...

Owners

• Team: Testing
• Most appropriate slack channel to reach out to: #g_testing
• Best individual to reach out to: @morefice, @jheimbuck_gl

Expectations

What are we expecting to happen?

When geo is enabled and a pipeline artifact is created it should get replicated with geo.

What might happen if this goes wrong?

What can we monitor to detect problems with this?

If we can monitor the geo nodes and use our verification to make sure everything gets replicated correctly.

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

• @jheimbuck_gl could you help to set up the rollout plan for this feature please?
  • Update the steps to ping the PM/EM for groupgeo to assist with testing as noted in the comment.

Roll Out Steps

• Enable on staging (/chatops run feature set geo_pipeline_artifact_replication true --staging)
• Test on staging
• Ensure that documentation has been updated
• Ping @fzimmer and @nhxnguyen to coordinate remaining testing.
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=gitlab-org/gitlab codequality_mr_diff true)
• Enable on GitLab.com by running chatops command in #production (/chatops run feature set geo_pipeline_artifact_replication true)
• 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