Skip to content

[Feature flag]: Rollout of allow_immediate_namespaces_deletion feature flag

Production Change

Change Summary

Rollout of allow_immediate_namespaces_deletion feature flag for Disabling force-immediate deletion on SaaS (gitlab-org&19219)

Change Details

  1. Services Impacted - Immediate deletion of projects, immediate deletion of groups
  2. Change Technician - @peterhegman
  3. Change Reviewer - C4 does not require approval based on https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#approval-3
  4. Scheduled Date and Time (UTC in format YYYY-MM-DD HH:MM) - 2025-10-20 10:00PM UTC
  5. Time tracking - Less than 5 min, disable allow_immediate_namespaces_deletion feature flag
  6. Downtime Component - no downtime

Important

If your change involves scheduled maintenance, add a step to set and unset maintenance mode per our runbooks. This will make sure SLA calculations adjust for the maintenance period.

Preparation

Note

The following checklists must be done in advance, before setting the label changescheduled

Change Reviewer checklist

C4 C3 C2 C1:

  • Check if the following applies:
    • The scheduled day and time of execution of the change is appropriate.
    • The change plan is technically accurate.
    • The change plan includes estimated timing values based on previous testing.
    • The change plan includes a viable rollback plan.
    • The specified metrics/monitoring dashboards provide sufficient visibility for the change.

Change Technician checklist

  • The Change Criticality has been set appropriately and requirements have been reviewed.
  • The change plan is technically accurate.
  • The rollback plan is technically accurate and detailed enough to be executed by anyone with access.
  • This Change Issue is linked to the appropriate Issue and/or Epic
  • Change has been tested in staging and results noted in a comment on this issue.
  • A dry-run has been conducted and results noted in a comment on this issue.
  • The change execution window respects the Production Change Lock periods.
  • Once all boxes above are checked, mark the change request as scheduled: /label ~"change::scheduled"

Detailed steps for the change

Pre-execution steps

Note

The following steps should be done right at the scheduled time of the change request. The preparation steps are listed below.

Change steps - steps to take to execute the change

Estimated Time to Complete (mins) - 1 hr, enable for 25% each 15 min

  • Set label changein-progress /label ~change::in-progress
  • Enable feature flag for 25%
  • Enable feature flag for 50%
  • Enable feature flag for 75%
  • Enable feature flag for 100%
  • Set label changecomplete /label ~change::complete

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - Less than 5 min

Monitoring

Key metrics to observe

Edited by Peter Hegman