Repository navigation
Release v2.42.0
AuthProxy can now forward gRPC services, so a gRPC endpoint - a daemon's long-lived stream, say - can sit under its own path beside the application people sign in to on the same host.
Added
GrpcListeneropens an HTTP/2-only listener an ingress that terminates TLS can hand gRPC calls to. It runs the same pipeline as the public listener, and gRPC streams on it have no request body limit. See https://github.com/Cratis/AuthProxy/blob/main/Documentation/configuration/grpc-services.md.Protocol: Http2on a service endpoint forwards to a plain-HTTP backend over HTTP/2, which a gRPC backend needs.Default: trueon a service keeps the plain catch-all routes on it when other services are configured, so adding a service under its own path prefix no longer takes them away.