Open sjd78 opened 9 months ago
This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members.
cc: @ibolton336 , @dymurray
Summary
The keyclock theme in the https://github.com/konveyor/tackle-keycloak-theme repo should be updated to match the currently used version of keycloak. The theme seems to be referencing keycloak 12, while the operator is using keycloak 18.
Related to #113
Why
In most configurations of the operator, the container quay.io/konveyor/tackle-keycloak-init is used to initialize the keycloak container with a custom konveyor branding/theme. The tackle-keycloak-init container is generated from the repo https://github.com/konveyor/tackle-keycloak-theme. The further the keycloak theme drifts apart from the keycloak container, the higher the risk that the theme breaks keycloak functionality.
Considerations
The keycloak theme is only applied to the default upstream build. Any configurations or downstream builds of the operator that end up using RHSSO will not attempt to apply any themes.
References
Theme repo: https://github.com/konveyor/tackle-keycloak-theme
Where the theme pulls from keycloak: https://github.com/konveyor/tackle-keycloak-theme/blob/main/Dockerfile
Operator files that reference keycloak and theme versions:
Operator deployment template for keycloak container: https://github.com/konveyor/operator/blob/main/roles/tackle/templates/deployment-keycloak-sso.yml.j2#L36-L41