2022-04-11: change GitLab Pages write timeout to 5 minutes

Production Change

Change Summary

Provide a high-level summary of the change and its purpose.

Change Details

1. Services Impacted - ServicePages
2. Change Technician - @vshushlin
3. Change Reviewer - @mwasilewski-gitlab
4. Time tracking - unknown
5. Downtime Component - none

Detailed steps for the change

Pre-Change Steps - steps to be completed before execution of the change

Estimated Time to Complete (mins) - 10 min

• Set label changein-progress on this issue
• Merge gitlab-com/gl-infra/k8s-workloads/gitlab-com!1698 (merged) and deploy
• Visit https://staging.shushlin.dev/, make sure it opens succesfully

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 10 min

• Merge gitlab-com/gl-infra/k8s-workloads/gitlab-com!1697 (merged)
• Set label changecomplete on this issue

Post-Change Steps - steps to take to verify the change

Estimated Time to Complete (mins) - 1 min

• Visit https://shushlin.dev/, make sure it opens successfully
• Visit https://dashboards.gitlab.net/d/web-pages-main/web-pages-overview?orgId=1, make sure everything looks fine

Rollback

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

Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes

• Create Revert MR from Merge gitlab-com/gl-infra/k8s-workloads/gitlab-com!1697 (merged), merge it and deploy

Monitoring

Key metrics to observe

• Metric: Error rates
  • Location: https://dashboards.gitlab.net/d/web-pages-main/web-pages-overview?orgId=1
  • What changes to this metric should prompt a rollback: Higher error rates, lower apdex

Change Reviewer checklist

C4 C3 C2 C1:

• 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:

• 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.

Change Technician checklist

• This issue has a criticality label (e.g. C1, C2, C3, C4) and a change-type label (e.g. changeunscheduled, changescheduled) based on the Change Management Criticalities.
• This issue has the change technician as the assignee.
• Pre-Change, Change, Post-Change, and Rollback steps and have been filled out and reviewed.
• This Change Issue is linked to the appropriate Issue and/or Epic
• Necessary approvals have been completed based on the Change Management Workflow.
• 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.
• 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.)
• 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.
• 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.