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.

Sign up for GitHub

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

Jump to bottom

gRPC port is exposed even if gRPC is disabled #3494

Open
rexopl opened this issue Jan 22, 2024 · 3 comments
Open

gRPC port is exposed even if gRPC is disabled #3494

rexopl opened this issue Jan 22, 2024 · 3 comments

Comments

@rexopl
Copy link

rexopl commented Jan 22, 2024

consul-k8s/charts/consul/templates/client-daemonset.yaml

Lines 448 to 450 in 20a2397

- containerPort: 8502
hostPort: 8502
name: grpc

Disabling gRPC in client is not disabling node port 8502. It conflicts when consul server and client are on same node.
@d-mosinski-s
Copy link

Created pull request #3495

@d-mosinski-s
Copy link

Also noticed the same behavior is in server node port 8502 is enabled even if connect: is diabled.

@afischer-opentext-com
Copy link

Pull request #3816 also attempted to fix the issue. Does anyone now what needs to be done for getting at least a statement?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rexopl @afischer-opentext-com @d-mosinski-s