Kubernetes cluster pod status EVICTED

Question

Hey I've created a kubernetes cluster on linux. But I end up getting this error:

The connection to the server 172.30.250.79:6443 was refused - did you specify the right host or port?

And when I check my pods status, I get this:

kube-system   coredns-86c58d9df4-69zlx                   0/1     Evicted   0          5d23h   <none>          kmaster   <none>           <none>

kube-system   coredns-86c58d9df4-bt6lr                   0/1     Error     69         44h     <none>          kmaster   <none>           <none>

kube-system   coredns-86c58d9df4-f2wgx                   0/1     Evicted   0          45h     <none>          kmaster   <none>           <none>

kube-system   coredns-86c58d9df4-hr6lk                   0/1     Evicted   0          35m     <none>          kmaster   <none>           <none>

kube-system   coredns-86c58d9df4-jhrlt                   0/1     Evicted   0          47h     <none>          kmaster   <none>           <none>

kube-system   coredns-86c58d9df4-mgt8q                   0/1     Evicted   0          45h     <none>          kmaster   <none>           <none>

kube-system   coredns-86c58d9df4-qxgs6                   0/1     Evicted   0          6d20h   <none>          kmaster   <none>           <none>

kube-system   coredns-86c58d9df4-r2lg7                   0/1     Evicted   0          44h     <none>          kmaster   <none>           <none>

kube-system   coredns-86c58d9df4-s7kfr                   0/1     Evicted   0          6d20h   <none>          kmaster   <none>           <none>

kube-system   coredns-86c58d9df4-tr9cj                   0/1     Evicted   0          47h     <none>          kmaster   <none>           <none>

kube-system   coredns--XXXXX are in evicted state.

Answer 1

A pod gets evicted because of low resources in the node. Check the reason for eviction in Kubernetes events

Answer 2

You are running out of resources.This is due to: not enough memory,no node available, no node free, the image is not availble or not free.

For more information, refer to the Kubernetes Training.

Answer 3

There are three ways to determine why using kubectl.
- run `kubectl describe <EVICTED_POD>` to find out the reason why it was evicted in the events.
- run `kubectl describe <THE_NODE_WHERE_THE_POD_WAS_EVICTED>` to check Conditions. 
- run `kubectl get events`.

Answer 4

I learned this the hard way, but it's also better to have a guaranteed or burstable QOS intead of BestEffort, make sure that your pods are utilizing the resource you allocate it. Sometimes pods are evicted because it is using very little of the resource allocated to it and the other pods sharing the node needs the resource.