search

OpenUnison / openunison-k8s

Access portal for Kubernetes
Apache License 2.0
105 stars 5 forks source link

idc-proxy-ou-orchestra is not getting ready #43

Closed erkules closed 2 years ago

erkules commented 2 years ago

I delete and reinstalled an instance.

I0506 15:46:08.769431       1 secure_serving.go:200] Serving securely on [::]:8443
I0506 15:46:08.770693       1 dynamic_serving_content.go:131] "Starting controller" name="serving-cert::/etc/oidc/tls/crt.pem::/etc/oidc/tls/key.pem"
I0506 15:46:08.771267       1 tlsconfig.go:240] "Starting DynamicServingCertificateController"
E0506 15:46:08.840835       1 oidc.go:335] oidc authenticator: initializing plugin: 500 Internal Server Error: <?xml version="1.0" encoding="UTF-8" ?>
.... HTML OUTPUT....
E0506 15:46:18.862873       1 oidc.go:335] oidc authenticator: initializing plugin: 500 Internal Server Error: <?xml version="1.0" encoding="UTF-8" ?>

Im not how to debug this issue. it should be deployed the same way as 3 hour before :/ So because of that oidc-proxy does not become ready and the portal never starts.

In orchstra there is:

openunison-ou-orchestra-7d7f6db9c8-thnq4 openunison-ou-orchestra javax.servlet.ServletException: Unknown URI : /auth/idp/k8sIdp/.well-known/openid-configuration
openunison-ou-orchestra-7d7f6db9c8-thnq4 openunison-ou-orchestra [2022-05-06 16:32:46,534][XNIO-1 task-1] INFO  AccessLog - [Error] - UNKNOWN - https://127.0.0.1:8443/auth/idp/k8sIdp/.well-known/openid-configuration - cn=none - NONE [127.0.0.1] - [ff57cd76462974c2766bf0ea6d2de7dedb9b57afc]

Whats kinda awkward, as I run the same config on a second cluster.

mlbiam commented 2 years ago

Looks like the orchestra-login-portal helm deployment isn't installed?

erkules commented 2 years ago

Indeed I had a dependency on orchestra (and not operator) in flux. Now I need to find out why it worked in the first time /o\ thx