Nikolaos Moraitis
Nikolaos Moraitis
Same here. Is there any good approach?
@vektah This is a big blocker. Can you let us know if there is any workaround?
@vektah Can you elaborate on this one too? This is a blocker.
same here. This is a big blocker since it forces us to change the schema.
I think the problem I am facing is related to this one. https://github.com/keycloak/keycloak-operator/issues/586
@hokiegeek2 No luck...
@hokiegeek2 The keycloak-operator should create a `keycloak-discovery` service. Try to use that service to reach keycloak, instead
@hokiegeek2 In this case you will need to configure your ingress to use the same TLS as keycloak or tell your ingress to redirect the SSL. Check https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/tls.md
@lexcao I can't use http because I get another error: ``` net/http: HTTP/1.x transport connection broken: malformed HTTP response \"\\x15\\x03\\x03\\x00\\x02\\x02P\ ```
@lexcao Also, is there any way to change the internalURL in keycloak?