GitLab Next

What

Remove the :environment_tier feature flag ...

Owners

• Team: devopsrelease
• Most appropriate slack channel to reach out to: #s_release
• Best individual to reach out to: @shinya.maeda

Expectations

What are we expecting to happen?

By enabling the feature flag, the newly added environments.tier attribute will be automatically guessed/filled by the Deployments::UpdateEnvironmentWorker or Seed::Environment (i.e. pipeline creation).

You can see the full implementation in this MR.

What might happen if this goes wrong?

If the logic to set the tier on the application runtime has a problem, the process to create environments and pipelines (specifically with environment: keywords at jobs) could be aborted by an exception.

What can we monitor to detect problems with this?

We can monitor Sentry that there is no exception spike.

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

• gitlab-org/gitlab project
• gitlab-com/www-gitlab-com project

Roll Out Steps

• Enable on staging (/chatops run feature set environment_tier true --staging)
• Test on staging
• [-] Ensure that documentation has been updated => documentation will be added upon the feature flag removal.
• Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=gitlab-org/gitlab environment_tier true)
• 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
• Announce on the issue an estimated time this will be enabled on GitLab.com
• Enable on GitLab.com by running chatops command in #production (/chatops run feature set environment_tier 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

Rollback Steps

• This feature can be disabled by running the following Chatops command:

/chatops run feature set --project=gitlab-org/gitlab environment_tier false