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
Would it be possible to have a working example of a recommended way of how to install Keycloak 18 through the new operator in a production set-up with an Ingress/SSL and a customized quarkus image? Depending on the combination of settings I am using for the Keycloak CRD different things are not working, e.g. some URLs are still referencing /auth on the keycloak pages, some settings seem to point to https://URL:8443 instead of https://URL and if I try to correct those with settings I have some problems with invalid redirect uris.
Either Ingress with pass-through and TLS termination on the keycloak pod or Ingress with re-encrypt would be great to see how it should work.
Hello @fabland, thank you for your interest in the new Operator! I believe the issues you're facing are related to bugs we've found and we actually have a fix for: #12021
@vmuzikar already answered on the configuration/bugs side.
In general, having a full-blown "example" repository for the "production-ready" deployment we support seems like a good idea to me.
It might belong to the quickstart guides
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Would it be possible to have a working example of a recommended way of how to install Keycloak 18 through the new operator in a production set-up with an Ingress/SSL and a customized quarkus image? Depending on the combination of settings I am using for the Keycloak CRD different things are not working, e.g. some URLs are still referencing /auth on the keycloak pages, some settings seem to point to https://URL:8443 instead of https://URL and if I try to correct those with settings I have some problems with invalid redirect uris.
Either Ingress with pass-through and TLS termination on the keycloak pod or Ingress with re-encrypt would be great to see how it should work.
All reactions