Adding GKG Proxy to GDK

What does this merge request do and why?

Adding GKG Proxy

Addressing: #2970 (closed)

Where can I read more about these new services?

Please refer to the Design Document for more information: https://handbook.gitlab.com/handbook/engineering/architecture/design-documents/knowledge_graph/#container-architecture

How to set up and validate locally

Preparation

• Feel free to disable zoekt gdk config set zoekt.enabled
• Move the gitlab-zoekt-indexer to gitlab-zoekt-indexer-old. Make sure to rename it back after the testing.

Steps

1. Edit your gdk.yml by adding these lines

 knowledge_graph:
   auto_update: false
   enabled: true

Run gdk reconfigure afterwards.

2. gdk status should list the new GKG proxy service

|        | down 1368s    | gitlab-knowledge-graph-proxy-development-1   |
|        | down 1368s    | gitlab-knowledge-graph-proxy-development-2   |

3. Start the first proxy gdk start gitlab-knowledge-graph-proxy-development-1

4. It should register itself on Rails (Monolith). Check via rails console

Search::Zoekt::Node.all.map {|n| [n.id, n.uuid, n.services, n.created_at] }

You should see a new node being added with services = [1]

[8, "8708eef9-c8f0-4607-9a9e-6b07776ddd8c", [1], Tue, 30 Sep 2025 16:36:07.250579000 UTC +00:00]

Impacted categories

The following categories relate to this merge request:

• gdk-reliability - e.g. When a GDK action fails to complete.
• gdk-usability - e.g. Improvements or suggestions around how the GDK functions.
• gdk-performance - e.g. When a GDK action is slow or times out.

Merge request checklist

• This MR references an issue describing the change.
• This change is backward compatible. If not, please include steps to communicate to our users.
• Tests added for new functionality. If not, please raise an issue to follow-up.
• Documentation added/updated, if needed.
• Announcement added, if change is notable.
• gdk doctor test added, if needed.

Closes #2970 (closed)