Update the keycloak theme to match the current keycloak version #166
Labels
needs-kind
Indicates an issue or PR lacks a `kind/foo` label and requires one.
needs-priority
Indicates an issue or PR lacks a `priority/foo` label and requires one.
needs-triage
Indicates an issue or PR lacks a `triage/foo` label and requires one.
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
The text was updated successfully, but these errors were encountered: