Closed jronak closed 2 years ago
Base: 85.15% // Head: 85.22% // Increases project coverage by +0.07%
:tada:
Coverage data is based on head (
a7fd0f6
) compared to base (6d89c98
). Patch coverage: 100.00% of modified lines in pull request are covered.
:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
gRPC outbounds can be configured with client-provided TLS config via the
OutboundTLSConfigProvider
interface. Services can configure the outbound TLS like:Spiffe-ids provided in the config above are passed to
OutboundTLSConfigProvider.ClientTLSConfig
to fetch the client TLS config for the outbound. Exposes the following gRPC dialer options:OutboundTLSConfigProvider
- accepts outbound tls config provider instanceDialerTLSConfig
- accepts outbound tls config used in the tls dialerDialerDestinationServiceName
- accepts outbound name used in the tls dialer metricsdest
tagFor reviews, follow this order:
api/transport/tls/outbound.go
transport/grpc/options.go
transport/grpc/config.go