Hello all, We are currently trying to implement a software solution which will incorporate keycloak and will work under kubernetes. More specifically we will create a cluster of kubernetes pods. We have currently created a custom keycloak container images which extend the default keycloak image an…

I posted something similar on this topic a few days ago. There are a few tools for declarative configuration and synchronization of realm state. [image] Tools or approaches for Keycloak DML Changes Getting advice First of all, I wasn’t aware of “ Keycloakmigration ”. Thanks…

Thanks for the suggestions, I will have a look at them. It looks like we will probably end up defining the import process as a Job.

I have been using keycloak import strategy and importing a realm on each Keycloak startup. There is a few things you have to consider for this approach and there is some advantages and disadvantages: OVERWRITE_EXISTING Switching to the OVERWRITE_EXISTING strategy would allow you to store realm con…

Hello, Thanks for your response. We are actually also using a JSON based approach with the OVERWRITE_EXISTING strategy. The problem in our case is that we are currently doing it at startup, but this doesn’t seem like a good approach for a production env (where multiple pods create a cluster) where …

Idk, we have no issues in this case, ofc looking when traffic is lowest for release, also that is not something that you will do every day. Also what you can check with devops is to terminate all current pods after first is up, so there will be no 2 pods with different versions, and one pod will ser…

As xpg mentioned before, it’s hard to see the kc.sh import approach being used in a production environment. Luckily, we have the Terraform provider option. Now that Keycloak has adopted it, it’s hard to see a better approach. However, it all depends on the technology stack and experience.

Best way to import realm in keycloak cluster for prod environments (container based)

Getting advice

xgp March 8, 2025, 2:51pm 2

I posted something similar on this topic a few days ago. There are a few tools for declarative configuration and synchronization of realm state.

Most of the above can/should be run as a separate Job in k8s, or in some cases as an initContainer.

kc.sh import ... is good for dev or first time realm creation, but not good to run each time you start a container.

Topic		Replies	Views
How to change import strategy for Keycloak ob Kubernetes Configuring the server	15	378	February 1, 2025
Realm imported into master instead of creating a new one Getting advice	0	406	March 23, 2021
Import a realm when running with Docker? Configuring the server	2	2028	March 9, 2023
Keycloak 17 docker container : How to export/import realm? (import must be done on container startup) Getting advice container	28	37363	June 19, 2025
Keycloak 23 in Kubernetes is importing realm every single time	0	641	December 5, 2023

Best way to import realm in keycloak cluster for prod environments (container based)

Related topics