Сбой модуля kube-dns в пользовательском экземпляре ec2 со службой EKS
Я создаю кластер kubernetes в сервисе AWS EKS с пользовательским AMI. Мои узлы подключены к основным службам, но модуль kube-dns не работает. Вот журнал событий kube-dns pod.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 10m default-scheduler Successfully assigned kube-dns-7cc87d595-248cg to ip-10-131-65-47.us-west-2.compute.internal
Normal SuccessfulMountVolume 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal MountVolume.SetUp succeeded for volume "kube-dns-config"
Normal SuccessfulMountVolume 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal MountVolume.SetUp succeeded for volume "kube-dns-token-nvv9z"
Normal Pulling 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal pulling image "602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/kube-dns/kube-dns:1.14.10"
Normal Pulled 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal Successfully pulled image "602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/kube-dns/kube-dns:1.14.10"
Normal Pulling 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal pulling image "602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/kube-dns/dnsmasq-nanny:1.14.10"
Normal Pulling 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal pulling image "602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/kube-dns/sidecar:1.14.10"
Normal Created 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal Created container
Normal Pulled 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal Successfully pulled image "602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/kube-dns/dnsmasq-nanny:1.14.10"
Normal Started 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal Started container
Normal Pulled 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal Successfully pulled image "602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/kube-dns/sidecar:1.14.10"
Normal Created 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal Created container
Normal Started 10m kubelet, ip-10-131-65-47.us-west-2.compute.internal Started container
Warning Unhealthy 9m (x6 over 10m) kubelet, ip-10-131-65-47.us-west-2.compute.internal Readiness probe failed: Get http://10.131.66.61:8081/readiness: dial tcp 10.131.66.61:8081: getsockopt: connection refused
Warning Unhealthy 9m kubelet, ip-10-131-65-47.us-west-2.compute.internal Liveness probe failed: HTTP probe failed with statuscode: 503
Normal Created 9m (x2 over 10m) kubelet, ip-10-131-65-47.us-west-2.compute.internal Created container
Normal Started 9m (x2 over 10m) kubelet, ip-10-131-65-47.us-west-2.compute.internal Started container
Normal Pulled 9m kubelet, ip-10-131-65-47.us-west-2.compute.internal Container image "602401143452.dkr.ecr.us-west-2.amazonaws.com/eks/kube-dns/kube-dns:1.14.10" already present on machine
Warning BackOff 5m (x7 over 6m) kubelet, ip-10-131-65-47.us-west-2.compute.internal Back-off restarting failed container
Warning Unhealthy 3s (x19 over 9m) kubelet, ip-10-131-65-47.us-west-2.compute.internal Liveness probe failed: HTTP probe failed with statuscode: 503
Бревна кубеднс тара в стручках
Error from server: Get https://10.131.65.47:10250/containerLogs/kube-system/kube-dns-7cc87d595-248cg/kubedns: dial tcp 10.131.65.47:10250: getsockopt: no route to host
Логи dnsmasq в стручках
Error from server: Get https://10.131.65.47:10250/containerLogs/kube-system/kube-dns-7cc87d595-248cg/dnsmasq: dial tcp 10.131.65.47:10250: getsockopt: no route to host
Бревна коляски в стручке
Error from server: Get https://10.131.65.47:10250/containerLogs/kube-system/kube-dns-7cc87d595-248cg/dnsmasq: dial tcp 10.131.65.47:10250: getsockopt: no route to host