1

I have a server to server calls and I use GRPC (with .net core 5) It's working and test in local.

After that, I have moved all the services to Kubernetes Pod (Docker Desktop) and also tested through the flow (with swagger post-call) and it's working there too.

Now for monitoring, I added ISTIO and added the label to my namespace "istio-injection=enabled" restarted all my pods and now all are having 2 containers inside each pod.

I tested the basic services (again swagger) and it's working. when it comes to testing the GRPC call. The call is failing from the caller side saying

Grpc.Core.RpcException: Status(StatusCode="Unavailable", Detail="upstream connect error or disconnect/reset before headers. reset reason: protocol error")

I checked the logs at GRPC server-side and it has no clue about this call and the service is just running. then I am kind of thinking that error is coming from the caller side whereas it is not able to or make a call to GRPC server.

enter image description here

The error detail:

Grpc.Core.RpcException: Status(StatusCode="Unavailable", Detail="upstream connect error or disconnect/reset before headers. reset reason: protocol error") 
at Basket.API.GrpcServices.DiscountGrpcService.GetDiscount(String productName) in /src/Services/Basket/Basket.API/GrpcServices/DiscountGrpcService.cs:line 21 
at Basket.API.Controllers.BasketController.UpdateBasket(ShoppingCart basket) in /src/Services/Basket/Basket.API/Controllers/BasketController.cs:line 47 at lambda_method7(Closure , Object ) 
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.AwaitableObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Obje

Again, I remove the Istio and tested and that's started working again (without changing anything) I added istio back and it started failing again. all other services are working with istio but not this call (This is only GRPC call I have).

Harsh Manvar
  • 27,020
  • 6
  • 48
  • 102
Brijesh Shah
  • 573
  • 6
  • 18
  • how you have installed istio, and configuration ? is mTLS is disabled and other protocol configs? – Harsh Manvar Nov 23 '21 at 18:09
  • try checking this nice example which will injecct the istio sidecar as the pilot instead of envoy : https://github.com/istio/istio/tree/master/samples/grpc-echo – Harsh Manvar Nov 23 '21 at 18:10
  • It's so weird. I found the answer at https://istiobyexample.dev/grpc/ where it says - name: grpc # important! – Brijesh Shah Nov 23 '21 at 23:42
  • @BrijeshShah did you found a solution? If so, please post it as an answer, and accept it. –  Nov 24 '21 at 09:48

1 Answers1

4

I found a solution at https://istiobyexample.dev/grpc/ where it describes the missing item.

istio recommends using the name and version tag as Label but more importantly when working with GRPC, the service that exposes the GRPC needs to have the port name GRPC.

I have added that restarted the service and it got started working as expected. Again it's not something I resolved. All credit goes to the link https://istiobyexample.dev/grpc/ and the image posted below.

enter image description here

Brijesh Shah
  • 573
  • 6
  • 18