-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gRPC health checks creation #4996
Comments
Hi @jasonwilliams14 thanks for reporting! Be sure to check out the docs and the Contributing Guidelines while you wait for a human to take a look at this 🙂 Cheers! |
We have tests that currently pass with this scenario, we need to investigate them. |
To provide some more context, we need to remove |
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: