2022-10-19: Enable the artifacts CDN

Production Change

Change Summary

This change will enable the Artifacts CDN in Production.

• Readiness review readiness#54 (closed)
• Runbook https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/google-cloud-storage/artifacts-cdn.md
• Dashboard https://dashboards.gitlab.net/d/google-cloud-storage-artifacts-cdn/google-cloud-storage-artifact-cdn-detail?from=now-12h&to=now&var-PROMETHEUS_DS=Global&var-environment=gprd&var-stage=main&orgId=1

Change Details

1. Services Impacted - ServiceCI Runners
2. Change Technician - @jarv
3. Change Reviewer - @ahmadsherif
4. Time tracking - 30 minutes
5. Downtime Component - none

Detailed steps for the change

Change Steps - steps to take to execute the change

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

• Set label changein-progress /label ~change::in-progress
• Confirm that the feature flag doesn't exist yet on production
• Ensure gitlab-com/gl-infra/k8s-workloads/gitlab-com!2187 (merged) is merged and the secret is created, and that the key is correct.
• Merge gitlab-com/gl-infra/k8s-workloads/gitlab-com!2196 (merged) and validate that the CDN config is set on one of the pods with the correct secret key.

grep cdn: /srv/gitlab/config/gitlab.yml

• Start the rollout of ci_job_artifacts_cdn feature flag gitlab-org/gitlab#373860 (closed)
• 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) - Estimated Time to Complete in Minutes

• /chatops run feature set ci_job_artifacts_cdn false
• Revert gitlab-com/gl-infra/k8s-workloads/gitlab-com!2196 (merged)
• Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

• Artifacts CDN dashboard https://dashboards.gitlab.net/d/google-cloud-storage-artifacts-cdn/google-cloud-storage-artifact-cdn-detail?from=now-12h&to=now&var-PROMETHEUS_DS=Global&var-environment=gprd&var-stage=main&orgId=1
• logs for artifact download https://log.gprd.gitlab.net/goto/ea117e10-4fa0-11ed-b0ec-930003e0679c

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.