-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
v7.42.0 OIDC Discovery URL #21057
Comments
Hello @jlhawkins-stuff |
@jlhawkins-stuff could you please explain why do you want to use chectl v7.41.1 to deploy lower version of Che? |
@svor Fresh installs of che 7.42.0 using chectl 7.42.0 wasn't installing an OIDC (keycloak). Which required using the @tolusha Che 7.40.0 was deployed with chectl 7.41.1. That deployment was successful. chectl was updated to 7.42.0, then the server was updated to 7.42.0. That update was successful except for the gateway pod. That pod was accessing the wrong URL |
@jlhawkins-stuff |
I was watching this because it is happening to me as well but it got closed! I simply upgraded from 7.38 to 7.42 and the fourth container (the oauth-proxy) pod fails trying to fetch |
@barrygear I closed the issue because a fresh install of 7.42.0 did resolve THIS issue. Installing 7.42.0 had a whole host of other learning experiences. I'd be down to share experiences. I ultimately reverted to 7.38.0 cause I could get it working. |
Describe the bug
Upgrading CHE from 7.40.0 to 7.42.0 causes gateway (aka traefik) to fail oauth-proxy
Che version
7.42@latest
Steps to reproduce
New gateway 7.42.0 pod:
Expected behavior
https://keycloak-eclipse-che.che.example.com/auth/realms/che/.well-known/openid-configuration
provides a non 404 response.
Runtime
Kubernetes (vanilla)
Screenshots
No response
Installation method
chectl/latest
Environment
other (please specify in additional context)
Eclipse Che Logs
No response
Additional context
vsphere infrastructure
juju charmed Kubernetes deployment
The text was updated successfully, but these errors were encountered: