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 port is exposed even if gRPC is disabled #3495

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

d-mosinski-s
Copy link

@d-mosinski-s d-mosinski-s commented Jan 22, 2024

Changes proposed in this PR

Disable gRPC node port 8502 when client gRPC is disabled

How I've tested this PR

Added changelog and tests.
It was also tested by running modified chart from local code.

How I expect reviewers to test this PR

gRPC node port 8502 should be disabled in consul client when client.grpc is disabled. Currently it is conflicting with server grpc node port when running server and client same node.
Similar if should be applied to server template (do not expose 8502 when connect: is disabled) but maybe in different PR.

Checklist

@hashicorp-cla
Copy link

hashicorp-cla commented Jan 22, 2024

CLA assistant check
All committers have signed the CLA.

@d-mosinski-s d-mosinski-s changed the title gRPC node port disable when gRPC is not enabled gRPC port is exposed even if gRPC is disabled Jan 22, 2024
@d-mosinski-s
Copy link
Author

d-mosinski-s commented Jan 23, 2024

Added changelog and tests.
It was also tested by running modified chart from local code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants