kube-dns

问题 I have deployed a mongo db, Spring Boot BE, Angular app within GKE. My FE service is a load balancer, it needs to connect with my BE to get data but I'm getting an console error in my browser: GET http://contactbe.default.svc.cluster.local/contacts net::ERR_NAME_NOT_RESOLVED . My FE needs to consume /contacts endpoint to get data. I'm using DNS from my BE service (contactbe.default.svc.cluster.local) within my Angular app. It is my yml file that I used to create my deployment: apiVersion: v1

问题 We currently have pods in a kubernetes cluster (AKS) that need to resolve two different domains. The first domain beeing the cluster domain default.svc.cluster.local and the second one beeing mydns.local how can this be achieved? 回答1: I found the solution myself. There are two ways to achieve the desired name resolution: If your AKS Cluster is within an Azure VNET you can set the DNS settings in the VNET to the custom DNS Server that is able to resolve your custom domain. If your Pods have no

问题 I tried the following command on my minikube setup to verify if dns is working fine or not. kubectl exec -ti busybox -- nslookup kubernetes.default but this is the output I am getting ' Server: 10.96.0.10 Address 1: 10.96.0.10 nslookup: can't resolve 'kubernetes.default' command terminated with exit code 1' Apart from that, I checked the coredns pod logs it shows something like below: ` 2019-11-07T12:25:23.694Z [ERROR] plugin/errors: 0 5606995447546819070.2414697521008405831. HINFO: read udp

问题 Trying to understand why I'm seeing this output from my kube-proxy logs W0328 08:00:53.755379 1 server.go:468] Failed to retrieve node info: nodes "ip-172-31-55-175" not found W0328 08:00:53.755505 1 proxier.go:249] invalid nodeIP, initialize kube-proxy with 127.0.0.1 as nodeIP The cluster is working just fine, is that indicating an issue with the cluster configuration? 回答1: Can you please show the output of the command kubectl get node ? Probably the registered name used when kubelet starts

问题 I have setup my kubernetes cluster from scratch following this doc: https://kubernetes.io/docs/getting-started-guides/scratch/ My kubernetes master and worker are working correctly, but I didn't find the instruction to deploy dns addons. 回答1: Addons can be deployed through yaml files as well as using the addon manager . I have already installed dashboard , monitoring , DNS manually using the yaml files provided (with small modifications) in this repo. Please note addon-manager is pretty

问题 I have setup my kubernetes cluster from scratch following this doc: https://kubernetes.io/docs/getting-started-guides/scratch/ My kubernetes master and worker are working correctly, but I didn't find the instruction to deploy dns addons. 回答1: Addons can be deployed through yaml files as well as using the addon manager . I have already installed dashboard , monitoring , DNS manually using the yaml files provided (with small modifications) in this repo. Please note addon-manager is pretty

问题 I have installed a Kubernetes with Kubeadm tool, and then followed the documentation to install the Web UI (Dashboard). Kubernetes is installed and running in one node instance which is a taint master node. However, I'm not able to access the Web UI at https://<kubernetes-master>/ui . Instead I can access it on https://<kubernetes-master>:6443/ui . How could I fix this? 回答1: The URL you are using to access the dashboard is an endpoint on the API Server. By default, kubeadm deploys the API

问题 My ingress controller is working and I am able to access the service outside the cluster using http://(externalIP)/path using an HTTP GET request from a RestClient. However, I had to specify the "Host" header with value = "host" (value of my Ingress Resource) for this to work. Because of this, I am not able to hit http://(externalIP)/path from my web browser. Is there any way I can enable access from my external web browser without having to specify "Host" in the request header? Ingress

问题 I am trying to learn DNS in kubernetes with https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/ I deployed the busybox kubectl get pods busybox -o wide NAME READY STATUS RESTARTS AGE IP NODE busybox 1/1 Running 0 16m 10.200.1.5 worker-1 kubectl exec -ti busybox -- nslookup kubernetes.default Server: 10.32.0.10 Address 1: 10.32.0.10 kube-dns.kube-system.svc.cluster.local nslookup: can't resolve 'kubernetes.default' command terminated with exit code 1 Do I need to

问题 I've created a kubernetes cluster from scratch as the directions of Kelsey Hightower. As I checked, everything works without any error but after I've deployed my first application, I figured out my application couldn't resolve the DNSes. I've checked my coredns logs and saw below entries : .:53 2018/10/16 12:31:45 [INFO] CoreDNS-1.2.2 2018/10/16 12:31:45 [INFO] linux/amd64, go1.11, eb51e8b CoreDNS-1.2.2 linux/amd64, go1.11, eb51e8b 2018/10/16 12:31:45 [INFO] plugin/reload: Running