Skip to content

[Feature flag] Bulk delete of runners from the admin view

Summary

This issue is to rollout Select individual runners to delete from the ad... (#339525 - closed) on production, that is currently behind the admin_runners_bulk_delete feature flag.

Owners

Stakeholders

Expectations

What are we expecting to happen?

When is the feature viable?

What might happen if this goes wrong?

What can we monitor to detect problems with this?

Consider mentioning checks for 5xx errors or other anomalies like an increase in redirects (302 HTTP response status)

What can we check for monitoring production after rollouts?

Consider adding links to check for Sentry errors, Production logs for 5xx, 302s, etc.

Rollout Steps

Rollout on non-production environments

  • Ensure that the feature MRs have been deployed to non-production environments.
    • /chatops run auto_deploy status 6b199864
  • Enable the feature globally on non-production environments.
    • /chatops run feature set admin_runners_bulk_delete true --dev
    • /chatops run feature set admin_runners_bulk_delete true --staging
  • Verify that the feature works as expected. Posting the QA result in this issue is preferable.

Specific rollout on production

  • Ensure that the feature MRs have been deployed to both production and canary.
    • /chatops run auto_deploy status <merge-commit-of-your-feature>
  • This is an admin feature, so it is enabled in the entire instance:
    • /chatops run feature set admin_runners_bulk_delete true
  • Verify that the feature works on the specific entries. Posting the QA result in this issue is preferable.

Preparation before global rollout

  • Check if the feature flag change needs to be accompanied with a change management issue. Cross link the issue here if it does.
  • Ensure that you or a representative in development can be available for at least 2 hours after feature flag updates in production. If a different developer will be covering, or an exception is needed, please inform the oncall SRE by using the @sre-oncall Slack alias.
  • Ensure that documentation has been updated (More info).
  • Announce on the feature issue an estimated time this will be enabled on GitLab.com.
  • Notify #support_gitlab-com and your team channel (more guidance when this is necessary in the dev docs).

Global rollout on production

For visibility, all /chatops commands that target production should be executed in the #production slack channel and cross-posted (with the command results) to the responsible team's slack channel (#g_TEAM_NAME).

Release the feature

After the feature has been deemed stable, the clean up should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase.

You can either create a follow-up issue for Feature Flag Cleanup or use the checklist below in this same issue.

  • Create a merge request to remove admin_runners_bulk_delete feature flag. Ask for review and merge it.
    • Remove all references to the feature flag from the codebase.
    • Remove the YAML definitions for the feature from the repository.
    • Create a changelog entry.
  • Ensure that the cleanup MR has been deployed to both production and canary. If the merge request was deployed before the code cutoff, the feature can be officially announced in a release blog post.
    • /chatops run auto_deploy status c966c058515f67c5014545981d1988d4ec8e1a47
  • Close Select individual runners to delete from the ad... (#339525 - closed) to indicate the feature will be released in the current milestone.
  • Clean up the feature flag from all environments by running these chatops command in #production channel:
    • /chatops run feature delete admin_runners_bulk_delete --dev
    • /chatops run feature delete admin_runners_bulk_delete --staging
    • /chatops run feature delete admin_runners_bulk_delete
  • Close this rollout issue.

Rollback Steps

  • This feature can be disabled by running the following Chatops command:
/chatops run feature set admin_runners_bulk_delete false

Related to #339525 (closed)

Edited by Miguel Rincon