microsoft / mindaro

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

Bridge to Kubernetes on a namespace with many services #173

Open VamKon opened 3 years ago

VamKon commented 3 years ago

Is your feature request related to a problem? Please describe. Hello, I have tried the isolation mode of Bridge to Kubernetes (BtK) on a namespace with about 50 different pods (different micro services). BtK wants to setup 2 additional pods for each pod that is running for envoy routing and additional pods for the service that I am debugging. As you can imagine this explodes the number of pods currently running and also the resources they consume. This is just for one developer. If multiple devs need to start a debugging session at the same time, then the total number of pods gets multiplied by that factor. This can get really expensive if used on a daily basis.

Describe the solution you'd like Unfortunately, I don't have a good solution for this. I will update if I think of any. I just wanted to provide this as feedback. Don't know of any other way to get in touch with you.

Describe alternatives you've considered I have tried the non-isolated mode and that probably would not work for our team on a daily basis, where multiple developers are trying to debug their services. Probably would work for a team debugging session as we have a dedicated namespace for each team for trying things out.

amsoedal commented 3 years ago

Hi @VamKon, thanks for sending this feedback. I'm making a note to bring this up to the team so we can discuss possible ways forward.

VamKon commented 3 years ago

Thanks a lot @amsoedal - why does it need 2 envoy pods? Why not one?

amsoedal commented 3 years ago

@VamKon I followed up with my colleague and apparently this was a design decision at the time, but we'd be interesting in moving forward with just one envoy pod. Would it be possible for you to reach out to us at BridgeToKubernetes@microsoft.com? That way we can provide you with beta bits to test once we have a fix for this!

VamKon commented 3 years ago

Thanks @amsoedal. I sent the email to the address you provided above.

amsoedal commented 3 years ago

@VamKon great! I can confirm we received it :) I'll follow up when we have an update.