Maybe https://quay.io/repository/hyperfoil/horreum-keycloak is a better tag

Maybe https://quay.io/repository/hyperfoil/horreum-keycloak is a better tag

In testing last week with RHTAP, the year-old version of this hyperfoil-maintained keycloak worked for me, while none of the upstream keycloak builds would work. However, after chatting w/ @johnaohara about it, at some point on Friday that image was updated without a new tag in quay, and now it no longer works for me w/ RHTAP either. I'm digging in more to try to find the problem.

Why do we need a separate image? can't we just use the published keycloak images? and we set the version of keycloak image to be the latest version that Horreum has been verified to work with?

@dustinblack I have reverted the quay.io/hyperfoil/horreum-keycloak image so that at least the operator still works.

@johnaohara From what I see, that custom image has is a /opt/keycloak/data/import/keycloak-horreum.json file to setup the horreum realm. In order to change to a keycloak image the procedure described in keycloak documentation should be followed.

Another thing to take into consideration is to use the keycloak operator, then apparently there is a Custom Resource to import the realm.

This also ties in with issue #13 to be able to configure the realm name.

Apparently, something keeps changing.

We need a stable image and configuration that we can rely on