Narrative

Almost every customer, if not all, using Red Hat build of Keycloak need to use themes to customize the Login pages of Keycloak with their corporate designed and specific look-and-feel themes.
While this is easily doable and maintainable for customers running with RHBK in non-OpenShift/non-containerized environments, it is cumbersome to achieve the same when running with OpenShift.
RH-SSO 7.x customers can do this with the container image for Openshift by leveraging the feature of image extensions, allowing them to inject themes through jar files packaging into the original Red Hat openshift image without having to recreate that image.
The similar capability is missing in RHBK, even though there is an unsupported way to do it by using the podTemplates feature and a shared storage with persistence volumes.
Even though it is considered a best practice for container images to be immutable, i.e. build a custom image if a customization is required, we should provided RHBK customers with the option to add themes without having to create and deploy a custom container image.
Customers, especially those migrating from RH-SSO to RHBK, want to have the same easy way to add themes into an operator/container based setup like it is available with RH-SSO.

Value Proposition

• Unlocks migration for existing RH-SSO customers, which see this as a big UX regression
• The approach to build a custom image based on the original one reduces the functionality of the Operator lifecycle.
• Simplify the operational tasks

Goals

• Provide users with the capability for adding custom themes for RHBK deployments in OpenShift environments
• Must NOT force creation of a custom image to achieve the same
• Test and Document how customers can implement and use this with RHBK running in OpenShift