apicurio-registry-operator
apicurio-registry-operator copied to clipboard
The liveness probe rely on the external storage
- The liveness probe rely on the external storage.
This caused the pod to be restarted when the database was under maintenance. The liveness probe returned this:
sh-4.4$ curl http://localhost:8080/health/live
{"details":"Error id d1a65d60-fe15-4267-8014-e2aa67ea96ec-4","stack":""}
and after a few failures the pod was killed.
As per best practices, the liveness probe should not fail if the db is down, only the readiness.