Skip to content
This repository has been archived by the owner on Aug 20, 2022. It is now read-only.

using an ingress controller causes the extension to break the cluster #305

Open
Popeye4242 opened this issue Mar 17, 2022 · 0 comments
Open

Comments

@Popeye4242
Copy link

Popeye4242 commented Mar 17, 2022

Describe the bug
When starting a minimal application with Bridge to kubernetes, the kubernetes cluster becomes unresponsive. You cannot access it in any means using kubectl.
I have tested this with the traefik ingress controller. If you deploy traefik, then deploy the app and then start the bridge to kubernetes debug adapter, then kubernetes will refuse any connection.

I can still make connections through browser to traefik, but the local app will not be served because of Bad Gateway. When restarting Docker Desktop the process will resume where it stopped and everything works like intended.

To Reproduce

helm repo add traefik https://helm.traefik.io/traefik
helm repo update
helm install traefik traefik/traefik

git clone https://github.com/Popeye4242/WebApplication3.git
cd WebApplication3
docker build . -f ./WebApplication3/Dockerfile -t webapplication3:stable
cd WebApplication3/charts
helm install web .\webapplication3\ --namespace web --create-namespace

Launch the application from visual studio with the Bridge to Kubernetes configuration

Environment Details
Client used (VS Code/Visual Studio): Visual Studio
Client's version: 17.1.1
Operating System: Windows 10 Enterprise 20H2

Additional Information
It appears that the extension is terminating the docker backend.
image

@Popeye4242 Popeye4242 changed the title Bridge makes the kubernetes cluster become unresponsive using an ingress controller causes the extension to break the cluster Mar 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant