Code change:
What keywords did you search in Kubernetes issues before filing this one? (If you have found any duplicates, you should instead reply there.): vSphere, "message": "no endpoints available for service "kube-dns"", kube-dns, etc -- similar issues include: however it's not quite the same Is this a BUG REPORT or FEATURE REQUEST? (choose one): Bug Kubernetes version (use ): Environment: Cloud provider or hardware configuration: vSphere OS (e.g. from /etc/os-release): Using provided vmdk Kernel (e.g. ): and Install tools: GOVC + the script What happened: Our environment utilizes the RFC1918 10.0.0.0/8 block, so I edited to utilize an address space we are not using. This is my current configuration: After the deployment is finished, I am able to login to the dashboard via the URL provided via , however, when I check the DNS server I see: When I list services, I see: When I start a container and try to ping kube-dns, I am unable to: I can ping external IP addresses: Here's the configuration on each minion and the master: What you expected to happen: I expect containers can reach ping eachother. How to reproduce it (as minimally and precisely as possible): I've reproduced this problem using both 172.16.0.0/16 addresses as well as the 192.168.0.0/16 addresses. Anything else do we need to know: I followed the documentation here: and the only change I made was to the network configuration.
I just noticed that doesn't include any routes for the service IPs I defined (e.g. has no routing table entries on any of the minions, only ). I'm not sure how to fix it, but it looks like the DNS server can make requests to the upstream DNS, it just can't get responses back.
cc
Some additional info I probably should have included the first time:
I just noticed that while from inside a container I can ping google: I cannot ping our internal DNS which is at IP . So I think I'm getting closer to where the problem actually is. I also think the 192.168.120.120 was not actually unreachable, just not pingable. For example: Returns right away, while doing the same to IP hangs. I'm not sure why when using our DNS in the of my master/minions doesn't seem to give them the ability to resolve internal assets on our network.
Can you provide your output for iptables also
Hi imkin, Sure thing! Minion 1 - 10.248.30.38 Minion 2 - 10.248.30.40 Minion 3 - 10.248.30.37 Minion 4 - 10.248.30.39 Master - 10.248.30.36 Let me know what else I can provide, I haven't had much time to continue troubleshooting this week, but getting this to work would be a really great template for building our bare metal deployment. Thanks! ZC
Can you try with DNSSERVERIP="192.168.128.120"
Hi - I will edit that in the initial configuration and re-up my cluster this morning to see if that helps things work out of the box so to speak. Thanks! ZC
Hey I have edited my configuration as follows: I have re-run the script and everything came up and validated. I am still experiencing the same behavior, however. I now see this in the logs for the DNS service via the dashboard: I see that the service can't be reached by kubectl either (it doesn't even return kube-dns like it did previously): I also notice that on the minions, none of them seem to have routes for the higher IP ranges:
This looks to be the same as posting a PR shortly.
Awesome!! Thanks - I'm grabbing the from your pull request and will re-open this issue if that did not resolve it (once it's closed by the merge).
In the second case [when your kube-dns had the ip 192.168.128.120] where was your kube-dns?
based on the logs you posted you were definitely impacted by the issue in but I am not sure if that is the only issue on going on your setup. Please let us know how the fix goes for your environment.
There is no route for 192.168.3.0/24

Related discussion:
text: MASTER_CPU=1 NODE_NAMES=($(eval echo ${INSTANCE_PREFIX}-minion-{1..${NUM_NODES}})) <del> NODE_IP_RANGES="10.244.0.0/16" </del> <ins> NODE_IP_RANGES="10.244.0.0/16" # Min Prefix supported is 16 </ins> MASTER_IP_RANGE="${MASTER_IP_RANGE:-10.246.0.0/24}" NODE_MEMORY_MB=2048 NODE_CPU=1