Kuberbetes - AWS EKS - Internal-IP is not assigned

5/12/2020

I've AWS EKS cluster in my organization for internal practice purpose.

Currently installed applications on this cluster are - Jenkins, Nexus, Spinnaker, Grafana, Prometheus

Now in order to save the cost and optimal usage, I used to scale up to 8 nodes every morning and down to 0 nodes every evening.

I've observed that sometimes when I wanted to see the kubectl logs or run kubectl exec command I used to get this error

Error from server: no preferred addresses found; known addresses: []

I've also found that in worker nodes Internal IPs are not assigned, may be due to that, this issue is occurring.

NAME                                        STATUS   ROLES    AGE    VERSION               INTERNAL-IP   EXTERNAL-IP   OS-IMAGE         KERNEL-VERSION                  CONTAINER-RUNTIME
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx   Ready    <none>   3h7m   v1.12.10-eks-aae39f   <none>        <none>        Amazon Linux 2   4.14.171-136.231.amzn2.x86_64   docker://18.9.9
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx   Ready    <none>   3h7m   v1.12.10-eks-aae39f   <none>        <none>        Amazon Linux 2   4.14.171-136.231.amzn2.x86_64   docker://18.9.9
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx   Ready    <none>   3h7m   v1.12.10-eks-aae39f   <none>        <none>        Amazon Linux 2   4.14.171-136.231.amzn2.x86_64   docker://18.9.9

Is it probably due to after I installed Prometheus ? because it seems after that only this issue has started. Please advise. Thanks

-- Jaydeep Soni
amazon-eks
amazon-web-services
eks
kubernetes

0 Answers