[Feature flag] Rollout of `load_balancing_for_bulk_cron_workers`
Feature
This feature uses the :load_balancing_for_bulk_cron_workers
feature flag!
Owners
- Team: groupglobal search
- Most appropriate slack channel to reach out to:
#g_global_search
- Best individual to reach out to:
@dgruzd
- PM:
@JohnMcGuire
Stakeholders
Rollout Timeline
-
Enable on staging ( /chatops run feature set load_balancing_for_bulk_cron_workers true --staging
) -
Test on staging -
If it is possible to perform an incremental rollout, this should be preferred. Proposed increments are: 10%
,50%
,100%
. Proposed minimum time between increments is 15 minutes. -
Coordinate a time to enable the flag with the SRE oncall and release managers - In
#production
mention@sre-oncall
and@release-managers
. Once an SRE on call and Release Manager on call confirm, you can proceed with the rollout
- In
-
Announce on the issue an estimated time this will be enabled on GitLab.com. Note: Once a feature rollout has started, it is not necessary to inform @sre-oncall
/@release-managers
at each stage of the gradual rollout. -
Enable on GitLab.com by running chatops command in #production
(/chatops run feature set load_balancing_for_bulk_cron_workers true
) -
Cross post chatops Slack command to #support_gitlab-com
(more guidance when this is necessary in the dev docs) and in your team channel -
Announce on the issue that the flag has been enabled -
Remove feature flag and add changelog entry. Ensure that the feature flag definition YAML file has been removed in the same MR that is removing the feature flag from the code -
After the flag removal is deployed, clean up the feature flag by running chatops command in #production
channel
Final Step
-
Close this rollout issue for the feature flag after the feature flag is removed from the codebase.
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set --project=gitlab-org/gitlab load_balancing_for_bulk_cron_workers false
Edited by Dmitry Gruzd