Using Concurrent Hash Map storage

Using a Concurrent Hash Map database is available for the new map storage. It can be enabled via the following settings in the .env file in the provision/kubernetes folder:

See Customizing the deployment for a list of all configuration options.

After every change, re-run the task command to apply the changes to the minikube instance. Task will trigger the necessary scripts and will use the minimal steps to update the minikube. Running rebuild.sh is not required: It will destroy the complete instance and will take a lot longer to complete.

The Concurrent Hash Map storage is built-in into Keycloak, no extra pod is started. Every time the Keycloak pod is restarted, the data is cleared.

Keycloak connects to the Concurrent Hash Map database pod inside minikube and populates the DB schema.

The data inside the Concurrent Hash Map store is not accessible from the outside of Keycloak.