search

microsoft / mindaro

Bridge to Kubernetes - for Visual Studio and Visual Studio Code
MIT License
307 stars 106 forks source link

"upstream connect error or disconnect/reset before headers. reset reason: connection failure" when trying to connect to bridged service #228

Open l0stmylife opened 2 years ago

l0stmylife commented 2 years ago

Describe the bug When trying to connect to a bridged service the error "upstream connect error or disconnect/reset before headers. reset reason: connection failure" is seen.

To Reproduce Launch a project with bridge to kubernetes and isolation mode enabled. Wait for the project to be ready. curl or visit the url and receive the "upstream connect error or disconnect/reset before headers. reset reason: connection failure" error message

Logs logs-bridge.zip

Environment Details Client used Visual Studio: Client's version: 16.9.2 Operating System: windows 10

Additional context This bug only happens in isolation mode and only to some projects. manually port-forwarding to services works so it's not a code problem on our end. Before the new containers are spun up we receive a standard 404 error so it does seem something is running.

pragyamehta commented 2 years ago

@l0stmylife Sometimes it can take upto a minute for the isolation mode to be setup. I would advise you to try running isolation mode and giving it a minute before you try hitting the URL. If you still see this error, please take a look at the pods in your namespace and see if any of them are recycling. Let us know what you observe.

l0stmylife commented 2 years ago

@pragyamehta Thank you for your reply, unfortunately no mather how long we wait this error persists.

all pods and services created by bridge seem to be running correctly and all other microservices work fine with bridge.

We are also sure the base microservice works correctly because we can port-forward to it directly without using bridge and confirm it works as expected.

Any further help would be appreciated.