Within the blogpost about Kubernetes, ideally, the liveness probe shouldn't use /actuator/health. If we do this, and let's say a database goes down, then /actuator/health goes DOWN, and the pod would be killed, which is not ideal (it's not the application their "fault").
A better approach would be to use /actuator/info or another custom endpoint.
Readiness probe should use /actuator/health, since the application is only ready to take traffic when the health is UP.
Within the blogpost about Kubernetes, ideally, the liveness probe shouldn't use /actuator/health. If we do this, and let's say a database goes down, then /actuator/health goes DOWN, and the pod would be killed, which is not ideal (it's not the application their "fault").
A better approach would be to use /actuator/info or another custom endpoint.
Readiness probe should use /actuator/health, since the application is only ready to take traffic when the health is UP.