Skip to content

Deploy Zoekt in GSTG

Dylan Griffith requested to merge 384723-deploy-zoekt-on-gstg into master

What does this MR do?

DRAFT This is draft as it will be rolled out in this CR gitlab-com/gl-infra/production#8598 (closed)

With gitlab-zoekt added as an optional dependency for the gitlab chart in gitlab-org/charts/gitlab!3018 (merged) we want to enable this on staging.gitlab.com . Initially we will just be enabling indexing and search with Zoekt for a small set of projects so we only need enough storage for our initial test group. We probably won't start with gitlab-org on staging as it's likely a bit wasteful to have all that duplicated storage. Instead we'll probably just make some smaller public group with searchable code (Zoekt will initially only work for public groups).

The overall epic for this work can be tracked in gitlab-org&9404 and the production readiness review can be found at gitlab-com/gl-infra/readiness!146 (merged) .

This MR depends on:

  1. gitlab-org/charts/gitlab!3018 (merged)
  2. gitlab-org/cloud-native/charts/gitlab-zoekt!7 (merged)
  3. gitlab-org/cloud-native/charts/gitlab-zoekt!8 (merged)

Why is it being deployed to the Regional cluster only?

Zoekt is a stateful service (similar to Postgres, Elasticsearch etc.) and we don't yet have a replication mechanism implemented (we will do this in gitlab-org/gitlab-build-images#118 (moved) and will need to address if that helps with Zonal cluster support). For now just running a Zoekt service in every zonal cluster would mean that each one would have their own random selection of indexed repos that don't correlate necessarily to the request being processed.

Author Check-list

Please read the Contributing document and once you do, complete the following:

  • Check if all of the following apply:
    • Assign to the correct reviewer per the contributing document
    • Apply the correct metadata per the contributing document
    • Link to related MRs for applying the changes on other environments
    • Link to related Chef changes
    • If necessary link to a Criticality 4 Change Request issue

Reviewer Check-list

  • Check if all of the following apply:
    • Reviewed the diff jobs to confirm changes are as expected
    • No changes shown in the diffs not associated with this MR - This may require a rebase or further investigation

Applier Check-list

  • Make sure there is no ongoing deployment for the affected envs before merging (see #announcements slack channel)

Closes #384723

Edited by John Skarbek

Merge request reports