Geo: Migrate Uploads replication to SSF. Roll out Issue
Summary
This issue is to rollout Geo: Migrate Uploads replication to SSF on production,
that is currently behind the geo_upload_replication
feature flag.
Owners
- Team: Geo team
- Most appropriate slack channel to reach out to:
#g_geo
- Best individual to reach out to: vsizov
- PM: Nick Nguyen
Stakeholders
The Rollout Plan
- Rollout on geo.staging.gitlab.com
The errors can be checked in https://sentry.gitlab.net/gitlab/geo-staging-gitlabcom/ and the Geo admin panel section
Expectations
What are we expecting to happen?
We expect all the uploads are synced using Geo Self Service Framework
What might happen if this goes wrong?
Uploads sync can be broken in any way.
What can we monitor to detect problems with this?
The errors can be checked in https://sentry.gitlab.net/gitlab/geo-staging-gitlabcom/ and the Geo admin panel section
Rollout Steps
-
Enabling the feature flag on staging -
Test the feature -
Enable the feature flag by default
Global rollout on production
-
Verify the change has the desired outcome. If not disable the feature /chatops run feature set geo_upload_replication false
WARNING: This approach has the downside that it makes it difficult for us to clean up the flag. For example, on-premise users could disable the feature on their GitLab instance. But when you remove the flag at some point, they suddenly see the feature as enabled and they can't roll it back to the previous behavior. To avoid this potential breaking change, use this approach only for urgent matters.
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set geo_upload_replication false