2022-12-29: Execute PDM for gprd

Production Change

Change Summary

This issue is reserved for executing PDM for gprd on 2022-12-29.

Reasons for this deployment:

• Reduce risk: to prevent commits from piling up and have a big deployment after the PCL lifts
• Business continuity: to allow a security release to be performed in the first week of January 2023.

Change Details

1. Services Impacted - GitLab.com
2. Change Technician - @mayra-cabrera
3. Change Reviewer - @mbursi
4. Time tracking - ~30m
5. Downtime Component - N/A

Detailed steps for the change

Change Steps - steps to take to execute the change

end of AMER working hours

• Inform EOC
• Set label changein-progress /label ~change::in-progress
• execute the PDM /chatops run post_deploy_migrations execute
• Package for which PDM was executed: 15.8.202212290620-d5b1b283fd4.2f0f30f3743
• [x Remove changein-progress and add changecomplete

Rollback

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

• [-] We don't execute rollbacks for PDMs

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.

C2 C1:

• [-] Check if the following applies:
  • The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
  • The change plan includes success measures for all steps/milestones during the execution.
  • The change adequately minimizes risk within the environment/service.
  • The performance implications of executing the change are well-understood and documented.
  • The specified metrics/monitoring dashboards provide sufficient visibility for the change.
    • If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
  • The change has a primary and secondary SRE with knowledge of the details available during the change window.
  • The labels blocks deployments and/or blocks feature-flags are applied as necessary

Change Technician checklist

• Check if all items below are complete:
  • The change plan is technically accurate.
  • 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.
  • For C1 and C2 change issues, the change event is added to the GitLab Production calendar.
  • For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (In #production channel, mention @sre-oncall and this issue and await their acknowledgement.)
  • For C1 and C2 change issues, the SRE on-call provided approval with the eoc_approved label on the issue.
  • For C1 and C2 change issues, the Infrastructure Manager provided approval with the manager_approved label on the issue.
  • Release managers have been informed (If needed! Cases include DB change) prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
  • There are currently no active incidents that are severity1 or severity2
  • If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.