-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
quay-v3.16.0
-
False
-
-
False
-
-
This is a bug affecting on-prem Red Hat Quay installations.
The /health endpoint returns a 404 Not Found
The issue is always reproducible:
# NOT WORKING $ oc exec -it <quay-pod-name> -- curl http://localhost:8080/health <html> <head><title>404 Not Found</title></head> <body> <center><h1>404 Not Found</h1></center> <hr><center>nginx</center> </body> </html> # WORKING $ oc exec -it quay-quay-app-d8764dbd6-gqbck -- curl http://localhost:8080/health/instance {"data":{"services":{"auth":true,"database":true,"disk_space":true,"registry_gunicorn":true,"service_key":true,"web_gunicorn":true}},"status_code":200}
The same endpoint works on Quay.io
$ curl https://quay.io/health {"data":{"services":{"auth":true,"database":true,"disk_space":true,"registry_gunicorn":true,"service_key":true,"web_gunicorn":true}},"status_code":200}
Documentation: https://docs.redhat.com/en/documentation/red_hat_quay/3/html/manage_red_hat_quay/health-check-quay#health-check-endpoints