Skip to content
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

Closed
ankushagarwal opened this issue Jun 7, 2018 · 5 comments · Fixed by #1537
Closed

Ambassador Version 0.34.0 causing DNS Issues on Worker Node #945

ankushagarwal opened this issue Jun 7, 2018 · 5 comments · Fixed by #1537

Comments

@ankushagarwal
Copy link
Contributor

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.

@ankushagarwal
Copy link
Contributor Author

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)

@ankushagarwal
Copy link
Contributor Author

/cc @kflynn

@ankushagarwal 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
@kflynn
Copy link
Contributor

kflynn commented 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.)

@ankushagarwal
Copy link
Contributor Author

@kflynn How do I do that?

@ankushagarwal
Copy link
Contributor Author

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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants