Following the tutoral gives a "socket hang up"

[buckleyGI]

Describe the bug
When following the Tutorial: Use Bridge to Kubernetes the endpoints becomes unavailable after the debugger is attached.
We get a "socket hang up" on the /api/todos endpoint

https://learn.microsoft.com/en-us/visualstudio/bridge/bridge-to-kubernetes-vs

We had the use the workaround described here microsoft/mindaro#26 (comment)

Note that everything is working find until the point we attach the debugger

Mention the platform you are using
Visual Studio 2022 17.3
Bridge to Kubernetes 2022 Version 3.1.20230118.1

To Reproduce

1. Follow the tutorial on https://learn.microsoft.com/en-us/visualstudio/bridge/bridge-to-kubernetes-vs
2. Stop After performing step 6 of "Connect to your cluster"
3. Observe that the endpoint /api/todos gives a "socket hang up"

Expected behavior
The tasks that were already entered

Screenshots
2 Screenshots:

1. The error that the front end gives
2. the endpoint that is in a faulty state

Desktop (please complete the following information):

• Windows 11 Enterprise Build 22000.co_release.210604-1628
• Firefox v 109.0

[hsubramanianaks]

@buckleyGI Thanks for raising this issue, we will look into it.

[hsubramanianaks]

@buckleyGI I am not able to reproduce (no socket hang up error) this with latest VS extension in VS 2022. This happens sometimes if you are connected to VPN and VPN blocks the socket? Can you try without VPN? Please let me know, thanks.

[buckleyGI]

Hi @hsubramanianaks Thanks for your reply. The VPN wasn't enabled
I am now at work (and thus without VPN) and now get "Refresh not supported".

[buckleyGI]

I redid the workaround as described here and can connect to the cluster again. The same message is given "socket hang up" at work without vpn

[hsubramanianaks]

@buckleyGI can you share the logs ? Thank you.

[Eneuman]

Hi @hsubramanianaks Thanks for your reply. The VPN wasn't enabled

I am now at work (and thus without VPN) and now get "Refresh not supported".

You can get around the "Refresh not supported" problem by running any kubectl command from a command window. The problem is that your token is expired and KubernetesClient does not yet support refreshing the token using your refresh token when using AKS.

This is where the error comes from:

https://github.com/kubernetes-client/csharp/blob/d38302d8f160ee706269864cf151c85ed3f8b5b6/src/KubernetesClient/KubernetesClientConfiguration.ConfigFile.cs#L480

[elenavillamil]

@buckleyGI can you confirm that running kubectl command solves your issue? If so I will go ahead and close this issue.

[elenavillamil]

Closing due ot inactivity but please feel free to re-open if you are still stuck.