Deploying keycloak with http (not https!) only

Describe the bug

It is possible to deploy keycloak, using the operator, in http (not https!) mode. Which makes sense for development setups, using e.g. Minikube or Kind.

However, in that case, e.g. the admin console doesn’t work, as it always redirects to https://, even if the port is 80:

This did work in 17 (legacy).

Version

18.0.0

Expected behavior

Allows to use plain HTTP.

Actual behavior

Wrongly redirects from http to https when opening the admin console.

How to Reproduce?

Use the following CR:

apiVersion: k8s.keycloak.org/v2alpha1
kind: Keycloak
metadata:
  name: sso
spec:
  hostname: sso.192.168.39.167.nip.io
  instances: 1
  serverConfiguration:
  - name: db
    value: postgres
  - name: db-url-database
    secret:
      key: database
      name: keycloak-db-secret
  - name: db-url-host
    secret:
      key: host
      name: keycloak-db-secret
  - name: db-url-port
    secret:
      key: port
      name: keycloak-db-secret
  - name: db-username
    secret:
      key: username
      name: keycloak-db-secret
  - name: db-password
    secret:
      key: password
      name: keycloak-db-secret
  - name: hostname-strict
    value: "false"
  - name: hostname
    value: sso.192.168.39.167.nip.io
  - name: hostname-port
    value: "80"
  - name: proxy
    value: passthrough
  tlsSecret: INSECURE-DISABLE

Anything else?

No response

[Wolfsrudel]

I’m stuck there too. I assume you have a proxy in front of it? I think it has something to do with the headers, but I haven’t been able to find a suitable combination of possible solutions that works. 😅

[ctron]

Do you think we can close this issue?

Of course!