-
Notifications
You must be signed in to change notification settings - Fork 267
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
CoreDNS timeout on vSphere cluster when resolve a service #8144
Comments
Thanks for reporting @ygao-armada. We are looking into this issue and will get back with any information we find. |
@sp1999 Some update, I find it's related to gpu-operator, look like, if we install argocd before gpu-operator, there is no such issue.
And I install gpu-operator with instruction from: https://github.com/NVIDIA/gpu-operator/blob/release-23.9/scripts/install-gpu-operator-nvaie.sh |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
In EKSA cluster for vSphere, we have a strange error, on worker node, if we replace the /etc/resolv.conf with that from pod argocd-server-xxx:
The nslook up command will resolve the IP (10.96.221.1) first, then wait for 10 seconds til timeout
We can see the IP (10.96.221.1) is correct as follows:
And 10.96.192.10 is the coredns IP:
Am I missing something?
What you expected to happen:
No timeout should happen for command "nslookup argocd-redis"
How to reproduce it (as minimally and precisely as possible):
Install argoCD on a EKSA vSphere cluster, and take the steps in above description.
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: