could not find service for endpoint "kube-controller-manager" in namespace "kube-system"

119 views
Skip to first unread message

Norman Khine

unread,
Aug 30, 2016, 3:29:19 AM8/30/16
to Kubernetes user discussion and Q&A
Hello, in my logs I am seeing the following:


Aug 24 15:18:28 kube-dns-v10-4epnq k8s_skydns.29528e52_kube-dns-v10-4epnq_kube-system_af513c8b-69f7:  2016/08/24 14:18:28 skydns: received DNS Request for "kubernetes.default.svc.cluster.local." from "127.0.0.1:36423" with type 1
Aug 24 15:18:28 kube-dns-v10-4epnq k8s_skydns.29528e52_kube-dns-v10-4epnq_kube-system_af513c8b-69f7:  2016/08/24 14:18:28 skydns: received DNS Request for "1.0.3.10.in-addr.arpa." from "127.0.0.1:53016" with type 12
Aug 24 15:18:29 kube-dns-v10-4epnq k8s_kube2sky.958e3886_kube-dns-v10-4epnq_kube-system_af513c8b-69:  I0824 14:18:29.522336       1 kube2sky.go:196] could not find service for endpoint "kube-scheduler" in namespace "kube-system"
Aug 24 15:18:30 kube-dns-v10-4epnq k8s_kube2sky.958e3886_kube-dns-v10-4epnq_kube-system_af513c8b-69:  I0824 14:18:30.218894       1 kube2sky.go:196] could not find service for endpoint "kube-controller-manager" in namespace "kube-system"
Aug 24 15:18:30 kube-dns-v10-4epnq k8s_healthz.d19e4a5b_kube-dns-v10-4epnq_kube-system_af513c8b-69f:  2016/08/24 14:18:30 Worker running nslookup kubernetes.default.svc.cluster.local 127.0.0.1 >/dev/null
Aug 24 15:18:30 kube-dns-v10-4epnq k8s_skydns.29528e52_kube-dns-v10-4epnq_kube-system_af513c8b-69f7:  2016/08/24 14:18:30 skydns: received DNS Request for "kubernetes.default.svc.cluster.local." from "127.0.0.1:53015" with type 28
Aug 24 15:18:30 kube-dns-v10-4epnq k8s_skydns.29528e52_kube-dns-v10-4epnq_kube-system_af513c8b-69f7:  2016/08/24 14:18:30 skydns: received DNS Request for "kubernetes.default.svc.cluster.local." from "127.0.0.1:38941" with type 1
Aug 24 15:18:30 kube-dns-v10-4epnq k8s_skydns.29528e52_kube-dns-v10-4epnq_kube-system_af513c8b-69f7:  2016/08/24 14:18:30 skydns: received DNS Request for "1.0.3.10.in-addr.arpa." from "127.0.0.1:45678" with type 12


have i missed something in the setup? i have a coreOS cluster on AWS
Reply all
Reply to author
Forward
0 new messages