You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating a gRPC health check for NGINX Ingress controller, the NGINX .conf being generated is incorrect.
Snippet from the error log:
[emerg] 320#320: invalid grpc parameter \"keepalive_time=60s\" in /etc/nginx/conf.d/vs_default_virtual-server.conf:132\n"
This is occuring when you specify the type: grpc in active health check section, or use grpcStatus, grpcService: ( I tested all of them in different variations, but behavior is the same)
Expected behavior
Defining a gRPC health check should correctly generate a NGINX .conf with the gRPC specific checks.
When using any of the gRPC specific checks, we should validate and ensure we are not adding HTTP checks.
Your environment
Tested in k3d and kind:
Tested NIC 3.3.0 to 3.4.2.
The text was updated successfully, but these errors were encountered:
To provide some more context, we need to remove keepalive_time from the configured output in the above thread . keepalive_time is not a valid setting when using gRPC health checks with NGINX.
When creating a gRPC health check for NGINX Ingress controller, the NGINX .conf being generated is incorrect.
Snippet from the error log:
This is occuring when you specify the
type: grpc
in active health check section, or usegrpcStatus
,grpcService
: ( I tested all of them in different variations, but behavior is the same)The generated .conf looks like the following:
The last bit,
keepalive_time=60s
is aHTTP
check and not allowed in gRPC.https://docs.nginx.com/nginx/admin-guide/load-balancer/grpc-health-check/#grpc-servers-that-accept-health-checking-protocol
Expected behavior
Defining a gRPC health check should correctly generate a NGINX .conf with the gRPC specific checks.
When using any of the
gRPC
specific checks, we should validate and ensure we are not addingHTTP
checks.Your environment
Tested in
k3d
andkind
:Tested NIC 3.3.0 to 3.4.2.
The text was updated successfully, but these errors were encountered: