-
Notifications
You must be signed in to change notification settings - Fork 160
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
Question: Do we need to have TLS on Core? #2010
Comments
If the answer is "Yes", what should it (flags) look like? |
it feels like the k8s dashboard arguments is probably not a terrible place to look for inspiration. Looks like they have Their recommended deployment creates some empty secrets for TLS certs and mounts them but (as far as I can see) doesn't actually configure the deployment to use them (by default it's accessed via http) but it seems they do some cert generation themselves @ boot time? tl;dr I don't think it's unreasonable to do tls on core but I think we should default to http as the dashboard does because, certainly for demo/getting started that's how people will use it. |
I think most of the cases we don't need TLS (most likely, it will be used behind an nginx/traefik/caddy ingress controler with tls), but enterprise should be able to handle that as some of the security compliances have full end-to-end encryption requirement and it included in-cluster communication too (FIPS, HIPA), so it's not enough to terminate the TLS connection on a load balancer and call backend without TLS. Question:
|
Using internal TLS is there, but not documented; and it is not "on" by default which is correct. Closing for now. |
While doing #1959, it was pointed out to me that:
And I asked:
To which I got a 🤷 .
So... why?
Acceptance Criteria
@JamWils will update with inverting the behavior so "certificates" are not required by default. A modern platform would secure this via load balancers and ingress policies.
The text was updated successfully, but these errors were encountered: