Kubernetes cluster pod status EVICTED

+1 vote

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

The connection to the server 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.
Jan 22 in Kubernetes by Neha

4 answers to this question.

0 votes

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

answered Jan 22 by Vishal
0 votes

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.

answered Jan 22 by Dinesh
0 votes

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 `
describe <THE_NODE_WHERE_THE_POD_WAS_EVICTED>` to check Conditions. 
- run `
kubectl get events`.

answered Jan 22 by Varsha
0 votes

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.

answered Jan 22 by Lyndon

Related Questions In Kubernetes

0 votes
1 answer

Pod status not ready always - kubernetes

I was having the same issue. In the ...READ MORE

answered Sep 6, 2018 in Kubernetes by Kalgi
• 45,780 points
0 votes
1 answer

automating cluster setup and app deplument on kubernetes

Go through Google Cloud Deployment Manager. it automates ...READ MORE

answered Jul 5, 2018 in Kubernetes by ajs3033
• 7,280 points
0 votes
3 answers

Kubernetes dashboard status-CrashLoopBackOff

I had the same issue, struggled for days. ...READ MORE

answered Apr 24 in Kubernetes by Bebo
0 votes
1 answer
0 votes
3 answers

Error while joining cluster with node

Hi Kalgi after following above steps it ...READ MORE

answered Jan 17 in Others by anonymous
+3 votes
1 answer
0 votes
1 answer

Pod stays in waiting in kubernetes cluster

If a Pod is stuck in the Waiting state, ...READ MORE

answered Oct 26, 2018 in Kubernetes by Kalgi
• 45,780 points
0 votes
2 answers

Pod status terminating-Kubernentes

Delete the finalizers block from resource (pod,deployment,ds ...READ MORE

answered Aug 29, 2018 in Kubernetes by Hannah
• 17,060 points