<p>When I execute <code>kubectl get pods</code>, I get different output for the same pod. </p>

<p>For example:</p>

<pre><code>$ kubectl get pods -n ha-rabbitmq
NAME            READY   STATUS    RESTARTS   AGE
rabbitmq-ha-0   1/1     Running   0          85m
rabbitmq-ha-1   1/1     Running   9          84m
rabbitmq-ha-2   1/1     Running   0          50m
</code></pre>

<p>After that I execute the same command and here is the different result:</p>

<pre><code>$ kubectl get pods -n ha-rabbitmq
NAME            READY   STATUS             RESTARTS   AGE
rabbitmq-ha-0   0/1     CrashLoopBackOff   19         85m
rabbitmq-ha-1   1/1     Running            9          85m
rabbitmq-ha-2   1/1     Running            0          51m
</code></pre>

<p>I have 2 master nodes and 5 worker nodes initialized with kubeadm. Each master node has one instance of built-in etcd pod running on them. </p>

<p>Result of <code>kubectl get nodes</code>:</p>

<pre><code>$ kubectl get nodes -owide
NAME              STATUS   ROLES    AGE     VERSION   INTERNAL-IP    EXTERNAL-IP   OS-IMAGE             KERNEL-VERSION      CONTAINER-RUNTIME
k8s-meb-master1   Ready    master   14d     v1.14.3   10.30.29.11    &lt;none&gt;        Ubuntu 18.04.2 LTS   4.15.0-51-generic   docker://18.9.5
k8s-meb-master2   Ready    master   14d     v1.14.3   10.30.29.12    &lt;none&gt;        Ubuntu 18.04.2 LTS   4.15.0-51-generic   docker://18.9.6
k8s-meb-worker1   Ready    &lt;none&gt;   14d     v1.14.3   10.30.29.13    &lt;none&gt;        Ubuntu 18.04.2 LTS   4.15.0-51-generic   docker://18.9.5
k8s-meb-worker2   Ready    &lt;none&gt;   14d     v1.14.3   10.30.29.14    &lt;none&gt;        Ubuntu 18.04.2 LTS   4.15.0-51-generic   docker://18.9.5
k8s-meb-worker3   Ready    &lt;none&gt;   14d     v1.14.3   10.30.29.15    &lt;none&gt;        Ubuntu 18.04.2 LTS   4.15.0-51-generic   docker://18.9.5
k8s-meb-worker4   Ready    &lt;none&gt;   14d     v1.14.2   10.30.29.16    &lt;none&gt;        Ubuntu 18.04.2 LTS   4.15.0-51-generic   docker://18.9.5
k8s-meb-worker5   Ready    &lt;none&gt;   5d19h   v1.14.2   10.30.29.151   &lt;none&gt;        Ubuntu 18.04 LTS     4.15.0-20-generic   docker://18.9.5
</code></pre>

<p>Can this issue be related to unsynchronized contents for the <code>/var/lib/etcd/</code> in the master nodes ?</p>

Cemal Unal
<p>Your pods are in <code>CrashLoopBackoff</code> state.
That means that some containers inside the pod are exiting (the main process exits) and the pod gets restarted over and over again.</p>

<p>Depending when you run the <code>get po</code> command, you might see your pod as <code>Running</code> (the process didn't exit yet) or <code>CrashLoopBackoff</code> (kubernetes is waiting before restarting your pod.</p>

<p>You can confirm this is the case by looking at the <code>Restarts</code> counter in the output.</p>

<p>I suggest you have a look at the restarting pods logs to get an idea why they're failing.</p>
