Geo: Migrate Container Repository replication to SSF. Roll out Issue
Summary
This issue is to rollout #337436 (closed) on production,
that is currently behind the geo_container_repository_replication
feature flag.
Owners
- Team: Geo team
- Most appropriate slack channel to reach out to:
#g_geo
- Best individual to reach out to: vsizov
- EM: Juan Silva
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 container repositories are synced using Geo Self Service Framework
What might happen if this goes wrong?
Container repositories 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 (no Geo on staging but I tested it on my own nodes) -
Test the feature -
Enable FF on staging /chatops run feature set geo_container_repository_replication true --staging
-
Enable FF on production /chatops run feature set geo_container_repository_replication true
-
Delete FF on prod and staging /chatops run feature delete geo_container_repository_replication
-
Enable the feature flag by default (!100750 (merged)) -
Remove the deprecated logic(!96419 (merged))
Global rollout on production
-
Verify the change has the desired outcome. If not disable the feature /chatops run feature set geo_container_repository_replication false
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set geo_container_repository_replication false
Edited by Valery Sizov