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

ping my nameserver fail #78926

JK-97 opened this issue Jun 12, 2019 · 2 comments


None yet
3 participants
Copy link

commented Jun 12, 2019

i use to this command deploy my k8s.
kubeadm init --pod-network-cidr=
and i want to deploy kubeflow on k8s.
but my problem is : pod in kubeflow namespeaces can not DNS,but can ping succes public network ip.
i use this comand to see the dns server:
cat /etc/resolv.conf
search kubeflow.svc.cluster.local svc.cluster.local cluster.local
options ndots:5

but at mster nodes ,i ping fail
i guess is the DNS server down


This comment has been minimized.

Copy link

commented Jun 12, 2019

@JK-97: There are no sig labels on this issue. Please add a sig label by either:

  1. mentioning a sig: @kubernetes/sig-<group-name>-<group-suffix>
    e.g., @kubernetes/sig-contributor-experience-<group-suffix> to notify the contributor experience sig, OR

  2. specifying the label manually: /sig <group-name>
    e.g., /sig scalability to apply the sig/scalability label

Note: Method 1 will trigger an email to the group. See the group list.
The <group-suffix> in method 1 has to be replaced with one of these: bugs, feature-requests, pr-reviews, test-failures, proposals.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.


This comment has been minimized.

Copy link

commented Jun 20, 2019

As is a Cluster IP, It is not ping-able. You can use telnet or curl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.