We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Description: Currently, extension manager loads the CA certificate when establishing GRPC connections:
gateway/internal/extension/registry/extension_manager.go
Line 271 in 5b6a35f
Connections are then cached and reused:
Line 219 in 5b6a35f
At this time, golang doesn't provide a convenient way to reload CA certificates: golang/go#64796. However, grpc-go's advancedtls library does support working with CA cert providers/callbacks: https://pkg.go.dev/google.golang.org/grpc/security/advancedtls#RootCertificateOptions.
advancedtls
Envoy Gateway can implement dynamic reload of the extension manager CA certificate by:
[optional Relevant Links:]
Any extra documentation required to understand the issue.
The text was updated successfully, but these errors were encountered:
Hi, I would like to work on this issue, please assign it to me.
Sorry, something went wrong.
sapirpol
Successfully merging a pull request may close this issue.
Description:
Currently, extension manager loads the CA certificate when establishing GRPC connections:
gateway/internal/extension/registry/extension_manager.go
Line 271 in 5b6a35f
Connections are then cached and reused:
gateway/internal/extension/registry/extension_manager.go
Line 219 in 5b6a35f
At this time, golang doesn't provide a convenient way to reload CA certificates: golang/go#64796. However, grpc-go's
advancedtls
library does support working with CA cert providers/callbacks: https://pkg.go.dev/google.golang.org/grpc/security/advancedtls#RootCertificateOptions.Envoy Gateway can implement dynamic reload of the extension manager CA certificate by:
[optional Relevant Links:]
The text was updated successfully, but these errors were encountered: