<p>I have 2 pod running of one deployment on kubernetes GKE cluster. I have scale this stateless deployment replicas to 2.</p>

<p>Both replicas almost started at same time both are restating with error code 137 ERROR. To change restart timing i have deleted one pod manually so that RS (replicaset) create new one. </p>

<p>Now again both pods are restarting at same time. Is there any connection between them ?. Both has to work independently. </p>

<p>i have not set a resource limit. In cluster free space upto 3 GB and deployment not taking much memory still getting 137 and restart in pods. </p>

<p>Why both pod restarting at same time that's issue? other all 15 microservices running perfectly. </p>

Harsh Manvar
<p>This is a common mistake when pods are defined. If you do not set a CPU and memory limit, there is no upper bound and the pod might take all resources, crash and restart. Those are discussed here [2][3]. You will also see that user “ciokan” [1] fixed his issue by setting the limit.</p>

<p>[1]<a href="https://github.com/kubernetes/kubernetes/issues/19825" rel="nofollow noreferrer">https://github.com/kubernetes/kubernetes/issues/19825</a>
[2]memory:<a href="https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/</a>
[3]CPU:<a href="https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/</a></p>
