[Feature flag] Rollout of `ci_remove_header_presence_check`

Summary

This issue is to roll out the feature on production, that is currently behind the ci_remove_header_presence_check feature flag.

Owners

  • Most appropriate Slack channel to reach out to: #g_pipeline-authoring
  • Best individual to reach out to: @lauraXD

Rollout Steps

Note: Please make sure to run the chatops commands in the Slack channel that gets impacted by the command.

Rollout on non-production environments

  • Verify the MR with the feature flag is merged to master and has been deployed to non-production environments with /chatops run auto_deploy status <merge-commit-of-your-feature>
  • Deploy the feature flag with /chatops run feature set ci_remove_header_presence_check --actors --dev --pre --staging --staging-ref
  • Verify that the feature works as expected. The best environment to validate the feature in is staging-canary as this is the first environment deployed to. Make sure you are configured to use canary.

Preparation before global rollout

  • Set a milestone to this rollout issue to signal for enabling and removing the feature flag when it is stable.
  • 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 exists for the feature, and the version history text has been updated.
  • Notify the #support_gitlab-com Slack channel 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 must be executed in the #production Slack channel and cross-posted (with the command results) to the responsible team's Slack channel.

  • Roll out in production:
    • Example: /chatops run feature set ci_remove_header_presence_check
    • Between every step wait for at least 15 minutes and monitor the appropriate graphs on https://dashboards.gitlab.net.

Monitor performance

dashboard

Cleanup

  • Create a merge request to remove the <feature-flag-name> feature flag. Ask for review/approval/merge as usual. The MR should include the following changes:
    • Remove all references to the feature flag from the codebase.
    • Remove the YAML definitions for the feature from the repository.
  • Ensure that the cleanup MR has been included in the release package. If the merge request was deployed before the monthly release was tagged, the feature can be officially announced in a release blog post: /chatops run release check <merge-request-url> <milestone>
  • Close [the feature issue][] to indicate the feature will be released in the current milestone.
  • Once the cleanup MR has been deployed to production, clean up the feature flag from all environments by running these chatops command in #production channel: /chatops run feature delete ci_remove_header_presence_check --dev --pre --staging --staging-ref --production
  • Close this rollout issue.

Rollback Steps

  • This feature can be disabled on production by running the following Chatops command:
/chatops run feature set ci_remove_header_presence_check false
  • Disable the feature flag on non-production environments:
/chatops run feature set ci_remove_header_presence_check false --dev --pre --staging --staging-ref
  • Delete feature flag from all environments:
/chatops run feature delete ci_remove_header_presence_check --dev --pre --staging --staging-ref --production
Edited by Laura Montemayor