You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I enable basic auth via BASIC_AUTH_ENABLE: true
I'm unable to complete a deployment on k8s due to failing startup probes. Workaround for now has been to disable the startup / liveness / readiness probes
I can confirm that the endpoint /api/result used for the health check requires credentials if basic auth is enabled.
running from debug container:
We get a 401 without creds: curl http://localhost:8080/api/result <!doctype html><html lang="en"><head><title>HTTP Status 401 – Unauthorized</title><style type="text/css">...
while if we provide the basic auth credentials, the healthcheck endpoint is available: curl -u admin:admin http://localhost:8080/api/result []#
Suggestion is to implement a standard endpoint /healthz which is exempt from auth and can be used by the k8s healthchecks
The text was updated successfully, but these errors were encountered:
If I enable basic auth via BASIC_AUTH_ENABLE: true
I'm unable to complete a deployment on k8s due to failing startup probes. Workaround for now has been to disable the startup / liveness / readiness probes
I can confirm that the endpoint
/api/result
used for the health check requires credentials if basic auth is enabled.running from debug container:
We get a 401 without creds:
curl http://localhost:8080/api/result <!doctype html><html lang="en"><head><title>HTTP Status 401 – Unauthorized</title><style type="text/css">...
while if we provide the basic auth credentials, the healthcheck endpoint is available:
curl -u admin:admin http://localhost:8080/api/result []#
Suggestion is to implement a standard endpoint
/healthz
which is exempt from auth and can be used by the k8s healthchecksThe text was updated successfully, but these errors were encountered: