Add BulkImports::PipelineWorker to imports shard to gprd

Production Change

Change Summary

MR for the change: gitlab-com/gl-infra/k8s-workloads/gitlab-com!1901 (merged)

This change request requests to add BulkImports::PipelineWorker to imports sidekiq shard for gprd environment. Similarly to RepositoryImportWorker, this worker performs import of project/group data, which sometimes can be a long time, and it needs to be uninterrupted. We moved RepositoryImportWorker to this shard as part of gitlab-org/gitlab#332616 (closed) and it makes sense to do the same for this worker, in order to eliminate potential future interruptions of this job by the auto-scaler.

As proposed in gitlab-com/gl-infra/k8s-workloads/gitlab-com!1901 (comment 1012741762) I am creating a change request for it.

This worker is already on imports shard on staging env and has been for more than a week gitlab-com/gl-infra/k8s-workloads/gitlab-com!1890 (merged)

Change Details

  1. Services Impacted - ServiceSidekiq
  2. Change Technician - @skarbek
  3. Change Reviewer - @georgekoltsov
  4. Time tracking - 30 minutes
  5. Downtime Component - 0

Detailed steps for the change

Change Steps - steps to take to execute the change

Estimated Time to Complete (mins) - 15 minutes

Rollback

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

Estimated Time to Complete (mins) - 15 minutes

Monitoring

Key metrics to observe

  1. import shard detail dashboard in Grafana
  2. Queued Jobs - any violation of any SLI or increase in the queue, we should revert this change.

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.
    • 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.)
    • 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.
Edited by John Skarbek