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
Ambassador Version 0.34.0 causing DNS Issues on Worker Node #945
Labels
Comments
To reproduce, create a single node gke cluster with n1-standard-8 worker node and 1.9.6-gke.1 k8s version and deploy kubeflow-core (with ambassador 0.34.0) |
/cc @kflynn |
ankushagarwal
changed the title
Ambassador Pods causing DNS Issues on Worker Node
Ambassador Version 0.34.0 causing DNS Issues on Worker Node
Jun 7, 2018
Can you see what exactly kube-dns is being asked to do? (I have a suspicion that I’d like to confirm.) |
@kflynn How do I do that? |
I can give you access to a cluster where I see this issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We recently updated to ambassador 0.34. When I deployed kubeflow on a single node cluster (n1-standard-8) kube-dns seems to be running at 100% CPU. Other processes are not able to resolve DNS on the host. Deleting the ambassador deployment fixes the DNS issue.
The text was updated successfully, but these errors were encountered: