gRPC Invocation Enablement
The self-managed Helmfile stack deploys grpc-proxy as a core service. Client
gRPC traffic reaches grpc-proxy through the Gateway TCP listener on port
10081.
Split or multi-cluster deployments need one additional route. During
invocation, a worker opens an HTTP/1 CONNECT callback channel to grpc-proxy on
port 10086. Enable this path when worker pods cannot route to grpc-proxy pod
IPs, such as when compute clusters and the control-plane cluster use separate
pod networks.
Single-cluster deployments usually do not need this worker callback route because workers can reach grpc-proxy pod IPs directly.
This TCP route is one way to give remote workers a callback path. The
Worker Callback Proxy is the other. It forwards
each callback to the pod that holds the request, so it works with more than one
grpc-proxy replica and also serves HTTP functions. Use one or the other: the
stack refuses to render when the proxy is enabled together with
grpcproxy.workerConnectBaseURL.
For a complete Amazon EKS installation example that compares single-cluster and multi-cluster topologies, see the CSP End-to-End Example.
Split or multi-cluster gRPC invocation over this TCP route is beta in 0.6.0.
It supports one grpc-proxy replica in the control plane. Set grpcproxy.replicaCount: 1 and
keep the grpc-proxy Horizontal Pod Autoscaler (HPA) disabled. Multiple
grpc-proxy replicas are not supported because the 0.6.0 worker callback route is
shared TCP routing and can send a callback to the wrong pod.
Network Paths
gRPC invocation uses two network legs:
The worker callback listener does not add HTTP/1 client invocation support. Client gRPC traffic still uses HTTP/2. Self-hosted HTTP/3 callback routing is out of scope for 0.6.0.
Add the Gateway Listener
Add a TCP listener for the worker callback path only when enabling split or
multi-cluster gRPC invocation. The listener name must match
ingress.gatewayApi.routes.grpcWorker.listenerName.
See Gateway Routing for where this listener fits in the Gateway quickstart.
Set Helmfile Values
Add these values to your environment file before deploying or syncing the control plane:
Set grpcproxy.workerConnectBaseURL to the base URL that workers can use to
reach the grpc-proxy callback listener. The stack passes this value to the
grpc-proxy chart, which renders the grpc-proxy container configuration. Do not
set the raw container environment variable directly.
For local multi-cluster testing with ncp-local, use:
After updating the environment file, continue with the normal Helmfile Installation flow.