feat(netbird): dedicated gRPC/relay Services with appProtocol; bump to 0.73.2#113
Merged
mikkeldamsgaard merged 1 commit intoJun 23, 2026
Conversation
…o 0.73.2 Fixes #104: gRPC and relay (WebSocket) traffic previously shared the main server Service, which has no appProtocol. Envoy-based Gateway API controllers (Cilium, Envoy Gateway) read a Service port's appProtocol to pick the upstream codec, so routing everything through the plain Service forced an HTTP/1.1 upstream and broke gRPC (needs h2c/HTTP-2) and WebSocket (needs upgrade handling). Adds two ClusterIP Services with the same selector as the main Service: - <release>-server-grpc with appProtocol kubernetes.io/h2c - <release>-server-relay with appProtocol kubernetes.io/ws server.grpcRoute and server.relayHttpRoute now auto-fill omitted backendRefs to these Services. Both are enabled by default and only render when their route is enabled; set enabled=false to fall back to the main Service. Route resource names are unchanged. relayTcpRoute (raw TCP) keeps defaulting to the main Service since appProtocol does not apply. Also bumps netbird appVersion 0.72.3 -> 0.73.2 (consolidates the upstream update issues). Upstream changes are internal stability/perf and posture-check hardening; no config, env var, port, protocol, or DB migration changes. Dashboard image stays at v2.39.0. Includes unit tests for the new Services and route fallbacks, extends the Gateway API e2e to assert backendRef targets and appProtocol values, and documents the Services (including the Cilium gatewayAPI.enableAppProtocol requirement) in the README. Closes #103, #104, #110, #111, #112 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mikkeldamsgaard
deleted the
chore/104-112-grpc-relay-services-and-netbird-bump
branch
This was referenced Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two things this round: a real chart bug fix (#104) and the consolidated upstream version bump.
Fix #104 — routes shared one Service with no
appProtocolgRPC and relay (WebSocket) traffic was routed through the main server
Service, which carries noappProtocol. Envoy-based Gateway API controllers (Cilium, Envoy Gateway) read a Service port'sappProtocolto pick the upstream codec, so a plain Service forced an HTTP/1.1 upstream — breaking gRPC (needs h2c/HTTP-2) and WebSocket (needs upgrade handling).This adds two
ClusterIPServices with the same selector as the main one:appProtocol<release>-server-grpckubernetes.io/h2cserver.grpcRouteonserver.grpcRoute<release>-server-relaykubernetes.io/wsserver.relayHttpRouteonserver.relayHttpRouteserver.grpcRoute/server.relayHttpRouteauto-fill omittedbackendRefsto these Services. Both are enabled by default (server.grpcService.enabled,server.relayService.enabled), render only when their route is enabled, and can be setfalseto fall back to the main Service. Route resource names are unchanged;relayTcpRoute(raw TCP) still targets the main Service. README documents the Services and the CiliumgatewayAPI.enableAppProtocol=truerequirement.netbird 0.72.3 → 0.73.2
Consolidates #103/#110/#111/#112. Upstream changes are internal (management/signal/relay stability & perf, posture-check hardening) — no config, env var, port, protocol, or DB-migration changes; dashboard image stays at v2.39.0.
Closes #103, #104, #110, #111, #112
How to verify
The Gateway API e2e now asserts the new backendRef targets and that the dedicated Services carry the correct
appProtocol:🤖 Generated with Claude Code