Closed cotepatrice closed 3 years ago
Thanks @cotepatrice for logging this issue! Sorry for the disruption of your experience, null references are indeed pretty shameful. :( I just provided a bit more details in the other issue you mention, that corresponds to the same problem: https://github.com/microsoft/mindaro/issues/177#issuecomment-850708633
I'm going to close this issue as duplicate, but please feel free to reply there, or reopen this one if I missed something and that this is different.
Closed as duplicate of https://github.com/microsoft/mindaro/issues/177
Describe the bug In Visual Studio 2019, Bridge To Kubernetes doesn't start anymore. I have a service in my local Docker Desktop cluster (default namespace). I tried to connect to it after setting all the right values in the configuration page (Kube Config Cluster: docker-desktop, Namespace: default, Service:, no routing isolation, application url : http://localhost:7778). When I try to launch the Bridge To Kubernetes debug, I get an "Object not set to an instance of an object" infamous error. It didn't prompt me for elevated permissions so that what seems to be the cause but I have no clue how to fix it. I looked at previous threads but can't seem to find a straight answer.
Logs bridge-mindarocli log :
bridge-library log :
Environment Details Client used : Visual Studio 2019 Version 16.9.4
Client's version: Operating System: Windows 10 Enterprise build 18363
UPDATE I just noticed the known issue about the presence of headless services in the cluster that may impact connection. As a matter of fact, I do have 2 MongoDb headless services in the cluster (mongodb-headless and mongodb-arbiter-headless). Maybe that's the problem.