-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get openIDConnect to work in 3.0.0-rc.13 and no logs output in UI pods #633
Comments
Will take a Look and see if I can improve logging |
@sarg3nt do you see no logs at all or no logs related to OpenIDConnect? Represents |
Can you set the UI image tag ( Your unhealthy error assumes that it is not able to start the server and already fails in the setup process. Does |
@fjogeleit No, scopes:
- openid
- profile
- email
claimMapping:
groups: "Group.Read.All" |
Could you set the https://kyverno.github.io/policy-reporter-docs/policy-reporter-ui/configuration.html#logging |
@fjogeleit sorry for the delay. |
Hm not really sure why it shows no logs at all. I released a new chart version where I added the Readiness and Liveness probes to the UI values. So you could try to disable both by overwrite ui:
livenessProbe:
httpGet: null
port: null
readinessProbe:
httpGet: null
port: null Hopefully this leads to an actual error and logs in the pod to investigate into. |
I'm trying to get
openIDConnect
to work in the new3.0.0-rc.13
.When I turn it on and configure it, the UI pods crash loop due to the health checks failing.
There are zero log lines being output, which makes debugging this kind of hard.
Usually I can get OIDC working with enough log reading and head banging and we do have it working in several other apps in our cluster (ArgoCD, Grafana, Oauth2Proxy, Headlamp, etc.)
I've tried changing / removing just about every value I can think of in the
openIDConnect
settings but get the same issue every time.With
openIDConnect
turned off, the UI works fine, so I know the ingress and everything else is set up correctly.I did read through: https://github.com/kyverno/policy-reporter/blob/2c98eac298d94cd8d5ef71bb6db16d6c8c82b863/docs/UI_AUTH.md
Values
This is a subset of the values.
I've tried removing the
groupClaim
and thescopes
with no luck. I doubt that's it as I don't know why that would cause the issue we are seeing.Events:
UI Secret
Below has senstaive values redacted and is from a run with no
scopes
orgroupClaim
Let me know if you need to see the rest of the helm
values.yaml
file.Is this a bug or am I doing something wrong.
The text was updated successfully, but these errors were encountered: