Liveness and Readiness Probes Fail for Spring Petclinic Sample App

[danielhelfand]

Following the steps in this tutorial and after implementing the workaround in #6, the Spring Petclinic sample app gets into a CrashLoopBackOff with the following errors:

FailedScheduling:

Warning  FailedScheduling  5m3s                   default-scheduler                      Binding rejected: Operation cannot be fulfilled on pods/binding "spring-petclinic-1-x2sct": pod spring-petclinic-1-x2sct is already assigned to node "ip-10-0-142-204.ec2.internal"

Liveness and Readiness Probe Issues:

Warning  Unhealthy         5s (x4 over 35s)   kubelet, ip-10-0-142-204.ec2.internal  Readiness probe failed: Get http://10.130.2.56:8080/: dial tcp 10.130.2.56:8080: connect: connection refused
Warning  Unhealthy         4s (x4 over 34s)   kubelet, ip-10-0-142-204.ec2.internal  Liveness probe failed: Get http://10.130.2.56:8080/: dial tcp 10.130.2.56:8080: connect: connection refused

Disabling the Liveness and Readiness probes in petclinic.yaml allows the application to successfully deploy through the example pipeline.