2023-04-12: Set registry us-east1-d in maintance mode

Production Change

Change Summary

We have an ongoing incident in which registry PATCH requests are degraded in us-east1-d.

In #8702 (closed) we've moved registry/registry-us-east1-d and registry/gke-cny-registry in DRAIN. This worked fine for stopping traffic, however, our deploy check started to fail and blocked deploys. Setting this to MAINT should allow the deployer checks to pass

Change Details

1. Services Impacted - ServiceRegistry
2. Change Technician - @steveazz
3. Change Reviewer - @jarv
4. Time tracking - 5min
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
• Maint registry/registry-us-east1-d: ./bin/set-server-state gprd maint registry/registry-us-east1-d
• Get server state: ./bin/get-server-state gprd registry/registry-us-east1-d
• Maint registry/gke-cny-registry: ./bin/set-server-state gprd maint registry/gke-cny-registry
• Get server state: ./bin/get-server-state gprd registry/gke-cny-registry
• 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

• ready registry/registry-us-east1-d: ./bin/set-server-state gprd ready registry/registry-us-east1-d
• Get server state: ./bin/get-server-state gprd registry/registry-us-east1-d
• ready registry/gke-cny-registry: ./bin/set-server-state gprd ready ^registry/gke-cny-registry
• Get server state: ./bin/get-server-state gprd ^registry/gke-cny-registry
• Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

• Metric: Registry RPS

  • Location: https://dashboards.gitlab.net/d/registry-regional/registry-regional-detail?orgId=1&viewPanel=1064354686
  • What changes to this metric should prompt a rollback: We should see us-east1-d RPS stay at 0

• Metric: Registry HPA / Pod Scaling

  • Location: Thanos Dashboard
  • What changes to this metric should prompt a rollback: We have a pod limit of 90 for our HPA. As we are draining 1 zone we expect traffic to increase to the remaining two zones, which will likely result in pod numbers scaling. At the moment we are well below limits and should not require any adjustments to the HPA limits. If we start hitting the HPA limit for any given zone we should look to increase the HPA value before making a rollback decision.

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.