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

Split TLS options for gRPC and HTTP #1709

Open
K3das opened this issue Feb 2, 2024 · 1 comment · May be fixed by #1870
Open

Split TLS options for gRPC and HTTP #1709

K3das opened this issue Feb 2, 2024 · 1 comment · May be fixed by #1870
Labels
enhancement New feature or request

Comments

@K3das
Copy link

K3das commented Feb 2, 2024

Why

Currently for a remote CLI you have no choice but to setup TLS. As a result, the public HTTP endpoints also end up encrypted, and in some configurations this sacrifices significant observability (currently my linkerd2 sidecar containers are unable to inspect traffic, monitor endpoint performance, and enforce per-route ACLs). While workarounds are possible (for example running headscale without TLS, and a proxy terminating TLS for gRPC), they would be far from ideal.

Description

One solution is adding split TLS options - to allow a user to enable TLS for gRPC, while not enabling it for other endpoints.

I'm happy to work on this if it's an acceptable change.

@K3das K3das added the enhancement New feature or request label Feb 2, 2024
@ohdearaugustin
Copy link
Collaborator

I see no issues if we split the configuration, as long it is a non breaking change.

@K3das K3das linked a pull request Apr 13, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants