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
We are installing Dex from helm chart v0.13.0 in k8s 1.24.
After installation there is no errors in pod logs, also there are:
{"level":"info","msg":"listening (telemetry) on 0.0.0.0:5558","time":"2023-03-20T12:03:05Z"}
{"level":"info","msg":"listening (http) on 0.0.0.0:5556","time":"2023-03-20T12:03:05Z"}
But when we are trying to reach Dex from browser by ingress, we get 404. We get the same error code when we are doing wget http://127.0.0.1:5556 inside pod.
The text was updated successfully, but these errors were encountered:
I am facing the same issue. I can reach the /healthz endpoint on the pod from another pod within the cluster, but the UI itself is unavailable.
I am using the "minimal configuration" state in the README. I tried the example ingress from the chart, I tried a Traefik ingressroute, until I found out that it is not actually the ingress controller erroring out, but the pod itself 404-ing...
Hmmm, after some more experimenting, I guess there is nothing wrong, there just is no content on the webUI. I mean, there is no WebUI, only the endpoints that are being hit by the clients.
We are installing Dex from helm chart v0.13.0 in k8s 1.24.
After installation there is no errors in pod logs, also there are:
But when we are trying to reach Dex from browser by ingress, we get 404. We get the same error code when we are doing
wget http://127.0.0.1:5556
inside pod.The text was updated successfully, but these errors were encountered: