title: spring-boot-kube-deployment-port80-3467990654-5c8nl 0/1 CrashLoopBackOff
body: <p>Steps followed during rolling updates:</p>
  
  <ul>
  <li>Create an image for the v2 version of the application with some changes</li>
  <li><p>Re-Build a Docker Image with Maven. pom.xml. Run command in SSH or Cloud Shell:</p>
  
  <pre><code>docker build -t gcr.io/satworks-1/springio/gs-spring-boot-docker:v2 .
  </code></pre></li>
  <li><p>Push the new updated docker image to the Google Container Registry. Run command in SSH or Cloud Shell</p>
  
  <pre><code>gcloud docker -- push gcr.io/satworks-1/springio/gs-spring-boot-docker:v2
  </code></pre></li>
  <li><p>Apply a rolling update to the existing deployment with an image update. Run command in SSH or Cloud Shell</p>
  
  <pre><code>kubectl set image deployment/spring-boot-kube-deployment-port80 spring-boot-kube-deployment-port80=gcr.io/satworks-1/springio/gs-spring-boot-docker:v2
  </code></pre></li>
  <li><p>Revalidate the application again through curl or browser</p>
  
  <pre><code>curl 35.227.108.89
  </code></pre>
  
  <p>and observe the changes take effect.</p></li>
  </ul>
  
  <p>When do we come across the "CrashLoopBackOff" error and how can we resolve this issue? Does it happen at application level or at kubernetes pods level?</p>