Skip to content
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 server can't be disabled #2477

Closed
lambdanis opened this issue May 28, 2024 · 0 comments · Fixed by #2826
Closed

gRPC server can't be disabled #2477

lambdanis opened this issue May 28, 2024 · 0 comments · Fixed by #2826
Labels
kind/bug Something isn't working

Comments

@lambdanis
Copy link
Contributor

lambdanis commented May 28, 2024

Tetragon Helm chart exposes an option to disable the gRPC server, but it doesn't work. With the following Helm values:

tetragon:
  grpc:
    enabled: false

the gRPC server is started on localhost:54321. In this case the server address isn't specified in the configmap, but the flag defaults to localhost:54321.

Moreover, when I set the grpc server address to an empty string:

tetragon:
  grpc:
    address: ""

the gRPC server started on :54321. This behaviour seems to be introduced by #896 which fixed a backwards incompatibility introduced by #552.

What I'd expect is that both of these configs disable the gRPC server.

@lambdanis lambdanis added the kind/bug Something isn't working label May 28, 2024
@kkourt kkourt self-assigned this May 28, 2024
@kkourt kkourt removed their assignment Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants