Issue in applying custom theme | keycloak operator | minikube

[abhishek upadhyay]

Hi Team,

I am facing issue in applying custom theme when using the legacy keycloak operator to run the keycloak service. I am using minikube windows setup for local kubectl. The issue start only when I add entry for custom theme jar in keycloak.yaml under extensions. when I removed the extensions entry, the keycloak pod is up and running with default theme. I followed this documentation link Server Installation and Configuration Guide (keycloak.org). I have provided the custom theme jar path which is valid one and can be accessed through a http URL.

Using the same custom theme jar I can successfully apply custom theme on when running keycloak in non-operator mode i.e. using Keycloak WildFly (deprecated) or new quarkus based.

The problem only occurs with operator mode deployment. Here is details of pod running after I deployed using my helm chart on local minikube. As you can see keycloak service pod has an issue. 

NAME                                  READY   STATUS                  RESTARTS         AGE
keycloak-0                                          0/1     Init:CrashLoopBackOff   26 (3m23s ago)   5h7m
keycloak-operator-86c869cbf5-9zz9x    1/1     Running                 0                5h8m
keycloak-postgresql-765cdc7fd-8xfxl   1/1     Running                 0                5h7m

If I check the log, I don't get much details in the log.

“Error from server (BadRequest): container "keycloak" in pod "keycloak-0" is waiting to start: PodInitializing”

Here is snippet of extensions entry in keycloak yaml file.

extensions:
    - https://github.com/aerogear/keycloak-metrics-spi/releases/download/2.5.3/keycloak-metrics-spi-2.5.3.jar
    - http://localhost:8080/keycloak/customtheme.jar
  externalAccess:
    enabled: True

Can you please help me on this?

Thanks,

Abhishek

[abhishek upadhyay]

Here is image that I am using.

containers:
- name: keycloak-operator
  image: quay.io/keycloak/keycloak-operator:18.0.0-legacy

[abhishek upadhyay]

Got in running finally in my local minikube setup. The issue was I have to use IP instead of localhost under extensions.  For minikube as I set it as hyperv as driver so, I have to use the minikube default switch IP

Thanks