-
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
Host File Entries Missing In Presence of Dapr #334
Comments
@messnerdev Thanks for raising this issue, I will check the demo and logs, I will get back once I triage the issue further. |
In my testing yesterday, I realized the host file entries also depend on which service I debug with Bridge to Kubernetes. Here's a more explicit summary: Attaching to the Deployment Service without a dapr sidecar (and all dapr infrastructure removed ) I see
Attaching to the Deployment Service with a dapr sidecar (and dapr infrastructure present) I see
Attaching to the StatefulSetA Service without a dapr sidecar (but the deployment service has a sidecar, and dapr infrastructure is present) I see
|
Hi @messnerdev, I checked the logs and see the below ports are called for withoutDapr. For further analysis can you please provide the logs of LPK remote agents. |
@Vidya2606, I'd be happy to, would you be able to provide guidance on how to obtain those? |
@messnerdev you can get the logs from the pod (the service/pod you are trying to debug) running in your cluster with image lpkremoteagent. |
I am having the same issue, so maybe I can also help out here. Logs with Dapr (where only Dapr gets forwarded to the local machine):
Logs without Dapr (where all available services are being forwarded):
|
Should we see an edited |
@robinmanuelthiel if the variable "useKubernetesServiceEnvironmentVariables" in tasks.json file is set to "true" then the host files will not be touched. Can you check this once and try. |
Describe the bug
When I use bridge to kubernetes (no isolation) without dapr, I see many host file entries added
As a result, my debug process can only communicate to other k8s services if the communication does not go through dapr
If I then stop bridge then add dapr (dapr init -k), then restart bridge (no isolation) I only get host file entries added
As a result, my debug process can only communicate to other k8s services if the communication goes through dapr
The services in my cluster use a combination of dapr and non-dapr communication patterns, and thus in both of the setups I have partially working communication.
There are recorded demos such as this, that seem to imply this was once possible (note how host file entries contain dapr and non-dapr mappings):
https://youtu.be/rxwg-__otso?si=9YbUKqfXYrstLUdh&t=197
Mention the platform you are using
Windows 10.0.19045 Build 19045 | VSCode 1.83.1 | Bridge v2.0.120231004 | .NET 7 | minikube
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Both dapr and non dapr services are exposed via host file
Screenshots
Can provide if needed
Logs:
WithDaprLogs.zip
WithoutDaprLogs.zip
Desktop (please complete the following information):
Additional context
One of the microservices is a StatefulSet if that matters.
The text was updated successfully, but these errors were encountered: