0
votes

Seeing error below :

"upstream connect error or disconnect/reset before headers. reset reason: connection failure" when tried with below steps:

have created AKS cluster and deployed ASP.NET core docker container. Have installed Istio as per instructions below: https://docs.microsoft.com/en-us/azure/aks/servicemesh-istio-install?pivots=client-operating-system-windows Have deployed ASP.NET core docker container in default namespace with istio-injection enabled. Here below is the virtual service and gateway yaml files.

After all this when trying to access http://52.224.26.59/Home/View where 52.224.26.59 is external ip of istio-ingressgateway getting error as "upstream connect error or disconnect/reset before headers. reset reason: connection failure".

enter image description here

1
can you fix the formatting? - Rinor
Yes added screen shot finding little difficulty to added code snippet with formating. - user2181334
1.Could you try to add name for your deployment service as mentioned here? 2.Could you try to check if bookinfo example works fine? - Jakub
it doesn't matter about metadata name for virtual service. Only we should keep on eye over getaway service referred with correct name. - user2181334

1 Answers

0
votes

I have resolved this issue.

It's because of an issue with an older version of .NET Core version. Once I updated with .NET Core 3.1, I was able to deploy and access .NET Core WebAPI.

Regarding other issues, there are more challenges and road is not clear with Istio and .NET core combination.