Skip to content

gitserver: Add HTTP clone port and health probes - #480

Merged
eseliger merged 1 commit into
mainfrom
eseliger/gitserver-http-clone-port
Sep 4, 2026
Merged

gitserver: Add HTTP clone port and health probes#480
eseliger merged 1 commit into
mainfrom
eseliger/gitserver-http-clone-port

Conversation

@eseliger

@eseliger eseliger commented Sep 4, 2026

Copy link
Copy Markdown
Member

Gitserver is gaining a dedicated HTTP clone listener so clone traffic can move away from the h2c gRPC port.

This declares the new http-clone port on 3179 and the existing debug server on 6060. It also replaces the TCP checks against the gRPC port with Gitserver's health contract: startup and readiness use /ready, while liveness uses /healthz.

The headless Service remains unchanged because it provides StatefulSet pod DNS; callers connect directly to pod-qualified Gitserver addresses. SRC_GIT_SERVERS remains on the gRPC port, 3178.

Prepare Kubernetes deployments for the dedicated Gitserver HTTP clone listener introduced in sourcegraph/sourcegraph#15346.

Declare the clone and debug ports, use the debug server readiness contract for startup and readiness, and use its health endpoint for liveness.

Amp-Thread-ID: https://ampcode.com/threads/T-01a06a40-0d1b-77ba-80e6-de55136092f1
Co-authored-by: Amp <amp@ampcode.com>
@eseliger eseliger changed the title feat/gitserver: add HTTP clone port and health probes gitserver: Add HTTP clone port and health probes Sep 4, 2026
@eseliger
eseliger marked this pull request as ready for review September 4, 2026 13:12
@eseliger
eseliger requested a review from a team September 4, 2026 13:12

@filiphaftek filiphaftek left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@eseliger
eseliger merged commit 8af5345 into main Sep 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants