-
Notifications
You must be signed in to change notification settings - Fork 411
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
cloud-proxy-server never has an external IP assigned #1867
Comments
I have removed the
But still,
|
I manually added the host to the hosts file:
Which at least resolve the address, but the connection to the server fails with a timeout
|
Anyone? |
Any suggestion on how I can solve this? |
Do you need more details? |
anyone? |
Hi @dcfranca. It's hard for us to debug issues in environments we don't officially support. I'm not too familiar with Colima. However, it seems like they have an option to enable exposing an external IP: https://github.com/abiosoft/colima/blob/main/docs/FAQ.md#the-virtual-machines-ip-is-not-reachable Have you tried running colima with that flag? |
Describe the bug
I'm deploying Pixie locally to a Colima cluster for testing and PoC purposes
Running
./dev_dns_updater
seems to get stuck, so I checked the LoadBalancer services and I have a weird situationAs you can see
vzconn-service
worked fine and has an IP assigned, but for some reasoncloud-proxy-service
doesn't have it, which I think might be the root cause for the issue withdev_dns_updater
If both didn't have an IP I would assume that there is something wrong with the load balancer assignment, but if worked for one, why didn't work for the other?
I checked the pod events for the service and pod, but I don't see anything wrong there
The only thing I see are some warnings on the cloud-proxy-server container, but I don't think they are an issue:
Any idea what could be preventing the service of getting an external IP?
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The External IP is assigned to the cloud-proxy-server
App information (please complete the following information):
The text was updated successfully, but these errors were encountered: