[Feature flag] Enable Helm charts MVC
Summary
This issue is to rollout the Helm charts MVC on production,
that is currently behind the helm_packages
feature flag.
Owners
- Team: Package
- Most appropriate slack channel to reach out to:
#s_package
- Best individual to reach out to: @sabrams / @10io
- PM: @trizzi
Stakeholders
The Rollout Plan
- Partial Rollout on GitLab.com with testing groups
- Rollout on GitLab.com for a certain period (How long)
- Percentage Rollout on GitLab.com
- Rollout Feature for everyone as soon as it's ready
https://dashboards.gitlab.net/d/api-rails-controller/api-rails-controller?orgId=1 (with the filter set on packages/helm
)
Testing Groups/Projects/Users
- TBD
Expectations
What are we expecting to happen?
What might happen if this goes wrong?
What can we monitor to detect problems with this?
Rollout Steps
Rollout on non-production environments
-
Ensure that the feature MRs have been deployed to non-production environments. -
/chatops run auto_deploy status <merge-commit-of-your-feature>
-
-
Enable the feature globally on non-production environments. -
/chatops run feature set helm_packages true --dev
-
/chatops run feature set helm_packages true --staging
-
-
Verify that the feature works as expected. Posting the QA result in this issue is preferable.
Preparation before production rollout
-
Ensure that the feature MRs have been deployed to both production and canary. -
/chatops run auto_deploy status 6c7acbdb
-
-
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. -
If the feature flag in code has an actor, enable it on GitLab.com for testing groups/projects. -
/chatops run feature set --project=issue-reproduce/packages/helm/helm-mvc helm_packages true
-
-
Verify that the feature works as expected. Posting the QA result in this issue is preferable.
Global rollout on production
-
Incrementally roll out the feature. - If the feature flag in code has an actor, perform actor-based rollout. Since this is a new isolated feature that, we can roll it out at once as it does not effect other features
-
/chatops run feature set helm_packages true
-
- If the feature flag in code has an actor, perform actor-based rollout. Since this is a new isolated feature that, we can roll it out at once as it does not effect other features
-
Announce on the feature issue that the feature has been globally enabled. -
Cross-post chatops slack command to #support_gitlab-com
. (more guidance when this is necessary in the dev docs) and in your team channel -
Wait for at least one day for the verification term.
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.
-
Create a merge request to remove helm_packages
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 above 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 74159ded
-
-
Close the feature issue 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 helm_packages --dev
-
/chatops run feature delete helm_packages --staging
-
/chatops run feature delete helm_packages
-
-
Close this rollout issue.
Rollback Steps
-
This feature can be disabled by running the following Chatops command:
/chatops run feature set helm_packages false
Edited by Steve Abrams