-
Notifications
You must be signed in to change notification settings - Fork 6
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
Avoid certificate generation when no TLS endpoint is configured #588
Comments
novoj
added a commit
that referenced
this issue
May 30, 2024
…gured Currently server generates or requires access to the certificates even if there is no TLS configured on any endpoint. Also we shouldn't generate and provide client certificates if MTLs is not configured. Also this patch changes how gRPC readiness probe works. Now Managed channel is used.
novoj
added a commit
that referenced
this issue
May 30, 2024
…on-when-no-tls-endpoint-is-configured fix(#588): Avoid certificate generation when no TLS endpoint is confi…
novoj
added a commit
that referenced
this issue
May 30, 2024
…gured Currently server generates or requires access to the certificates even if there is no TLS configured on any endpoint. Also we shouldn't generate and provide client certificates if MTLs is not configured. Also this patch changes how gRPC readiness probe works. Now Managed channel is used.
novoj
added a commit
that referenced
this issue
Jun 7, 2024
…gured Currently server generates or requires access to the certificates even if there is no TLS configured on any endpoint. Also we shouldn't generate and provide client certificates if MTLs is not configured. Also this patch changes how gRPC readiness probe works. Now Managed channel is used. (cherry picked from commit 8c31e2d)
novoj
added a commit
that referenced
this issue
Jun 7, 2024
…gured Currently server generates or requires access to the certificates even if there is no TLS configured on any endpoint. Also we shouldn't generate and provide client certificates if MTLs is not configured. Also this patch changes how gRPC readiness probe works. Now Managed channel is used. (cherry picked from commit 7ffed91)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently server generates or requires access to the certificates even if there is no TLS configured on any endpoint. Also we shouldn't generate and provide client certificates if MTLs is not configured.
The text was updated successfully, but these errors were encountered: