Skip to content
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

Open
kipusoep opened this issue Sep 8, 2023 · 6 comments
Open

Failed to resolve the ReplicaSet backing the service #313

kipusoep opened this issue Sep 8, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@kipusoep
Copy link

kipusoep commented Sep 8, 2023

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:

An unexpected error occurred: 'Failed to resolve the ReplicaSet backing the service '<redacted>-svc'.'

To see our active issues or file a bug report, please visit https://aka.ms/bridge-to-k8s-report.

For diagnostic information, see logs at 'C:\Users\<redacted>\AppData\Local\Temp\Bridge To Kubernetes'.

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:
image

@kipusoep kipusoep added the bug Something isn't working label Sep 8, 2023
@hsubramanianaks
Copy link
Collaborator

@kipusoep Thanks for raising this issue, seems like this is same as #267 , fix is in progress.

@kipusoep
Copy link
Author

Awesome, I did see that issue but didn't know it was the same issue down the road.

@hsubramanianaks
Copy link
Collaborator

@kipusoep do you use vscode extension , I can provide you VSIX to test this issue quickly ? Thanks, Please let me know.

@kipusoep
Copy link
Author

I use Visual Studio 2022.

@hsubramanianaks
Copy link
Collaborator

@kipusoep I will try to see if I can get you a VS 2022 extension to test and confirm on this. Thanks.

@hsubramanianaks
Copy link
Collaborator

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants