Configure the redis cache for registry in gprd

Production Change

Change Summary

Part of scalability#1953

Change Details

1. Services Impacted - ServiceRedis ServiceContainer Registry
2. Change Technician - @alejandro
3. Change Reviewer - @igorwwwwwwwwwwwwwwwwwwww
4. Time tracking - 2h30m
5. Downtime Component - 0

Detailed steps for the change

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 1h45

• Set label changein-progress /label ~change::in-progress
• Merge gitlab-com/gl-infra/k8s-workloads/gitlab-com!2198 (merged)
• Check that the cache is correctly configured in canary:
  • glsh kube use-cluster gprd
  • Wait for the redis cache configured successfully message to appear: stern -n gitlab-cny gitlab-cny-registry | grep -i redis
• Wait 30 minutes before moving to the next step
• Mark as ready and merge gitlab-com/gl-infra/k8s-workloads/gitlab-com!2199 (merged)
• Check that the cache is correctly configured in gprd-us-east1-b:
  • glsh kube use-cluster gprd-us-east1-b
  • Wait for the redis cache configured successfully message to appear: stern -n gitlab gitlab-registry | grep -i redis
• Wait 30 minutes before moving to the next step
• Rebase gitlab-com/gl-infra/k8s-workloads/gitlab-com!2155 (merged) after merging the previous MRs
• Mark as ready and merge gitlab-com/gl-infra/k8s-workloads/gitlab-com!2155 (merged)
• Check that the cache is correctly configured in each zone:
  • glsh kube use-cluster gprd-us-east1-c
  • Wait for the redis cache configured successfully message to appear: stern -n gitlab gitlab-registry | grep -i redis
  • glsh kube use-cluster gprd-us-east1-d
  • Wait for the redis cache configured successfully message to appear: stern -n gitlab gitlab-registry | grep -i redis
• 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) - 45

• Revert gitlab-com/gl-infra/k8s-workloads/gitlab-com!2155 (merged)
• Revert gitlab-com/gl-infra/k8s-workloads/gitlab-com!2199 (merged)
• Revert gitlab-com/gl-infra/k8s-workloads/gitlab-com!2198 (merged)
• Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

• Metric: Registry Service Apdex, and Registry Service Error Ratio
  • Location: https://dashboards.gitlab.net/d/registry-main/registry-overview?orgId=1
  • What changes to this metric should prompt a rollback: degradation violating SLOs
• Metric: Redis Registry Cache Service Apdex, and Redis Registry Cache Service Error Ratio
  • Location: https://dashboards.gitlab.net/d/redis-registry-cache-main/redis-registry-cache-overview?orgId=1
  • What changes to this metric should prompt a rollback: degradation violating SLOs

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.