pod in minikube can't access other services or connect to the internet #8949
Labels
kind/support
Categorizes issue or PR as a support question.
triage/needs-information
Indicates an issue needs more information in order to work on it.
Comments
priyawadhwa
added
the
kind/support
|
I got a same issue like this in Microsoft Windows 10 10.0.18362 Build 18362. |
|
Hey @neargle thanks for opening this issue. kube-dns is not available as an addon in minikube, we use coredns which is automatically enabled by kubernetes now. It looks like there's some networking issue if you can't connect to the internet. Could you provide the output of
to help with debugging? |
priyawadhwa
added
the
triage/needs-information
priyawadhwa
changed the title
|
@priyawadhwa Thx for reply. $ cat /etc/resolv.conf $ ping google.com -c 4 This is the output of I add apiVersion: v1
data:
Corefile: |
.:53 {
log
errors
health {
lameduck 5s
}
ready
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
fallthrough in-addr.arpa ip6.arpa
ttl 30
}
prometheus :9153
forward . /etc/resolv.conf {
max_concurrent 1000
}
cache 30
loop
reload
loadbalance
}
kind: ConfigMap
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","data":{"Corefile":".:53 {\n log\n errors\n health {\n lameduck 5s\n }\n ready\n kubernetes cluster.local in-addr.arpa ip6.arpa {\n pods insecure\n fallthrough in-addr.arpa ip6.arpa\n ttl 30\n }\n prometheus :9153\n forward . /etc/resolv.conf {\n max_concurrent 1000\n }\n cache 30\n loop\n reload\n loadbalance\n}\n"},"kind":"ConfigMap","metadata":{"annotations":{},"creationTimestamp":"2020-09-08T06:13:32Z","name":"coredns","namespace":"kube-system","resourceVersion":"205","selfLink":"/api/v1/namespaces/kube-system/configmaps/coredns","uid":"d61d3477-61fb-4a95-8dd4-e5c490e93393"}}
creationTimestamp: "2020-09-08T06:13:32Z"
managedFields:
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:data: {}
manager: kubeadm
operation: Update
time: "2020-09-08T06:13:32Z"
- apiVersion: v1
fieldsType: FieldsV1
fieldsV1:
f:data:
f:Corefile: {}
f:metadata:
f:annotations:
.: {}
f:kubectl.kubernetes.io/last-applied-configuration: {}
manager: kubectl-client-side-apply
operation: Update
time: "2020-09-09T06:52:33Z"
name: coredns
namespace: kube-system
resourceVersion: "90799"
selfLink: /api/v1/namespaces/kube-system/configmaps/coredns
uid: d61d3477-61fb-4a95-8dd4-e5c490e93393And all log since yesterday below: |
|
Hey @neargle looks like there's an issue with the could you try upgrading to minikube 1.13.1 and see if that resolves the issue? I know we've done some work around /etc/hosts in the past couple months |
|
Hey @neargle I'm going to go ahead and close this issue as it's been quiet for a few weeks. If you're still seeing this issue, feel free to reopen at any time by commenting /reopen! |
|
Sorry I open it up again as soon as you closed it. But i encounter this same error at this moment. I'm using minikube version v1.14.0 with Libvirt on Fedora 32 and no DNS resolution. using dnsutils image. I verified dns Service ClusterIP is 10.96.0.10 and endpoint is running and svc pointed to endpoints IP. |
|
Ok, so I keep making test. I deleted my k8s-workshop cluster so I can try it in stock configurations. With single node everything just works fine, with and without '-p' parameter When I try to create a multi node cluster, in this case with 3, no DNS resolution. |
|
minikube addons enable coredns ,I was able to solve my problem with the help of this . But still can't communicate between two container in different pods |
|
I am facing the same problem with minikube version: v1.13.1
|
|
Try this it got solved for me kubernetes/kubernetes#21613 (comment)
Thank me later! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I cannot get my services to communicate each other.
After I did
kubectl exec -it my-pod bashand executepingandcurl, I found that I cannot access other services and also have no access to the internet.In my /etc/resolve.conf inside my pod, I have
So it seems to be pointing at
kube-dns(10.96.0.10) but when I checked the addon, I dont havekube-dnsenabled.The text was updated successfully, but these errors were encountered: