kube-dns

问题 Setup The pods of the deployment named frontend are exposed via a service named frontend. NAME READY STATUS RESTARTS AGE po/frontend-b48b88789-dcxs6 1/1 Running 0 2h NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE deploy/frontend 1 1 1 1 2h NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE svc/frontend ClusterIP 10.106.243.125 <none> 80/TCP 2h Problem Querying via busybox the DNS name for the service frontend returns the services ip address. Querying via busybox the DNS name for the pod frontend

问题 I deployed a few VMs using Vagrant to test kubernetes: master: 4 CPUs, 4GB RAM node-1: 4 CPUs, 8GB RAM Base image: Centos/7. Networking: Bridged. Host OS: Centos 7.2 Deployed kubernetes using kubeadm by following kubeadm getting started guide. After adding the node to the cluster and installing Weave Net, I'm unfortunately not able to get kube-dns up and running as it stays in a ContainerCreating state: [vagrant@master ~]$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS

问题 I am deploying Kubernetes 1.4 on Ubuntu 16 on Raspberry Pi 3 following the instructions at http://kubernetes.io/docs/getting-started-guides/kubeadm/. The master starts and the minion joins no problem but when I add weave kubedns won't start. Here's the pods: k8s@k8s-master:~$ kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system etcd-k8s-master 1/1 Running 1 23h kube-system kube-apiserver-k8s-master 1/1 Running 3 23h kube-system kube-controller-manager-k8s

问题 is it possible to do a reverse DNS lookup from one pod to another in the same namespace on Kuberenetes? Setup: Kubernetes 1.5, kube-dns 1.9 When I exec a pod with nslookup I don't get a hostname but only a nslookup timeout like: $ time kubectl exec mypod -- nslookup 172\.18\.14\.13 nslookup: can't resolve '(null)': Name does not resolve Name: 172.18.14.13 Address 1: 172.18.14.13 real 0m5.592s mypod2 does have the internal IP 172.18.14.13. Both mypod and mypod2 have been deployed to the same

问题 I tried to setup a kubernetes dns addon based on ansible repo: https://github.com/kubernetes/contrib/tree/master/ansible/roles/kubernetes-addons After running the playbook, i can't find out neither dns pod nor service.!! After doing some lecture, (https://github.com/kubernetes/contrib/issues/886#issuecomment-216741889) it seems that i need to run the rc.yml and the svc.yml manually. that's what i did. Unfortunately, the dns pod and service still up for a while and suddenly terminates. I tried

问题 I use the skydns-rc.yaml.base(/kubernetes-release-1.3/cluster/addons/dns/sky..) file to create the k8s dns service. but the kubedns container is always failed to created. The following substitutions have been made: namespace: kube-system replaced by namespace: default __PILLAR__DNS__REPLICAS__ replaced by 1 __PILLAR__DNS__DOMAIN__ replaced by cluster.local __PILLAR__FEDERATIONS__DOMAIN__MAP__ deleted The edited element info and the whole file are shown below: apiVersion: v1 kind:

问题 I have a kubernetes cluster with several nodes. I have kube-dns running in 3 nodes. The issue I'm having is that if 1 of those 3 nodes goes down the requests between my pods/containers start to fail more or less 1 of 3 times. This is because when the container resolve a k8s service hostname it calls the kube-dns service to resolve that hostname and the kube-dns k8s services has three endpoints but one of those three endpoints is not valid as the node is down. K8s does not update the service

问题 Closed . This question needs to be more focused. It is not currently accepting answers. Want to improve this question? Update the question so it focuses on one problem only by editing this post. Closed last year . We are switching to using Kubernetes. It is simple to access other deployed services within a k8s deployment via the built in dns. So if I have pod/service named app1 and a pod/service named app2 and app1 needs to call app2, it can just use "app2" and k8s dns works its magic and

问题 I'm trying to connect to a postgres container running in docker on my mac, from my minikube setup in virtualbox. But I'm running into dns resolve issues. I'm running postgres as a container on docker > docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES a794aca3a6dc postgres "docker-entrypoint.s…" 3 days ago Up 3 days 0.0.0.0:5432->5432/tcp postgres On my Mac / VirtualBox / Minikube setup I create a service kind: Service apiVersion: v1 metadata: name: postgres-svc spec: type:

问题 I have a Kubernetes PetSet with name == elasticsearch and serviceName == es . It does create pods and, as expected, they have names like elasticsearch-0 and elasticsearch-1 . However, DNS does not seem to be working. elasticsearch-0.es does not resolve (nor does elasticsearch-0.default , etc.). If you look at the generated srv records they seem to be random instead of predictable: # nslookup -type=srv elasticsearch Server: 10.1.0.2 Address: 10.1.0.2#53 elasticsearch.default.svc.cluster.local