Skip to content

Register gRPC health check service on orchestrator server#3893

Open
Lazydayz137 wants to merge 1 commit intolivepeer:masterfrom
Lazydayz137:feat/2076-grpc-health-check
Open

Register gRPC health check service on orchestrator server#3893
Lazydayz137 wants to merge 1 commit intolivepeer:masterfrom
Lazydayz137:feat/2076-grpc-health-check

Conversation

@Lazydayz137
Copy link
Copy Markdown

What does this pull request do?

Registers the standard gRPC health checking protocol (grpc.health.v1.Health) on the orchestrator's gRPC server, enabling native Kubernetes gRPC health probes.

Specific updates

  • Register health.NewServer() on the gRPC server in StartTranscodeServer
  • Matches existing pattern used in router.go

How did you test each of these updates?

  • go test ./server/... passes
  • go vet ./server/... clean
  • gofmt clean

Does this pull request close any open issues?

Fixes #2076

Checklist

  • I have read the contribution guide
  • make and tests run successfully
  • Code is formatted with gofmt

Register the standard gRPC health checking protocol on the
orchestrator's gRPC server, matching the existing pattern used in the
Router server (router.go). This enables Kubernetes operators to use
native gRPC health probes or grpc-health-probe to monitor the actual
transcoding gRPC service rather than relying on the HTTP CLI endpoint.

The health server uses the default health.NewServer() which reports
SERVING status immediately, consistent with the router implementation.

Fixes livepeer#2076

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions github-actions bot added the go Pull requests that update Go code label Apr 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

go Pull requests that update Go code

Projects

Status: Triage

Development

Successfully merging this pull request may close these issues.

Register gRPC health check server when running gRPC server as an O

1 participant