You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a Kubenetes deployment with Istio or Linkerd, the grpc client created with @GrpcChannel("servicename") fails with a downstream protocol error (DSPE) / Invalid HTTP Header when calling the service.
If the grpc client is created with ManagedChannelBuilder.forTarget("servicename:port"), there are no errors.
While a Consul sidecar does not report the problem, both Istio and Linkerd sidecars (outbound) report the problem and kill the stream.
An example application (based on micronaut-grpc/examples/hello-world-kotlin), with additional detail and steps to produce, can be found here: https://github.com/SUMGlobal/dspe
The text was updated successfully, but these errors were encountered:
In a Kubenetes deployment with Istio or Linkerd, the grpc client created with @GrpcChannel("servicename") fails with a downstream protocol error (DSPE) / Invalid HTTP Header when calling the service.
If the grpc client is created with ManagedChannelBuilder.forTarget("servicename:port"), there are no errors.
While a Consul sidecar does not report the problem, both Istio and Linkerd sidecars (outbound) report the problem and kill the stream.
micronautVersion=2.0.2
micronautGrpcVersion = 2.0.5
kotlinVersion=1.3.72
kotlinxCoroutinesVersion=1.3.3
protocVersion=3.12.2
grpcVersion=1.29.0
grpcKotlinVersion=0.1.2
An example application (based on micronaut-grpc/examples/hello-world-kotlin), with additional detail and steps to produce, can be found here: https://github.com/SUMGlobal/dspe
The text was updated successfully, but these errors were encountered: