-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to resolve the ReplicaSet backing the service #313
Comments
Awesome, I did see that issue but didn't know it was the same issue down the road. |
@kipusoep do you use vscode extension , I can provide you VSIX to test this issue quickly ? Thanks, Please let me know. |
I use Visual Studio 2022. |
@kipusoep I will try to see if I can get you a VS 2022 extension to test and confirm on this. Thanks. |
@kipusoep The fix should be rolled out for VS 2022 in OCt 2023, can you retest and confirm if it is working, also please feel free to close this issue. Thank you. |
Describe the bug
When I try to run Bridge to Kubernetes with a service which has completed jobs inside of it, I get an error saying:
Mention the platform you are using
Running on AKS and connecting to it using VS2022.
Expected behavior
I would expect B2K to be able to connect to the running pods inside the service. But because the jobs have the same app label, they also belong to the service.
Screenshots

This is the situation:
The text was updated successfully, but these errors were encountered: