Repository navigation
|
Hello, I'm looking for some advice on the proper configuration of the Docker image for Keycloak 18-19. We have our own image of the Keycloak, including different providers, like Prometheus Metrics, Identity Providers, etc. This image is used across different environments with similar configurations, except for the database connection. On the developer's laptop, persistence is not needed, so no database is attached (I believe this is called Now we have the
Does the second option have an advantage over the first one? Like, some resources would be prepared and the Quarkus would only need to prepare the database things, or will it do the full optimization again (which doubles the startup time)? Thanks! |
Replies: 1 comment
|
I ended up using the auto-build option that is by default enabled in the Keycloak 19, which solved my problem. The startup penalty in the K8S stack was about 6 additional seconds |
I ended up using the auto-build option that is by default enabled in the Keycloak 19, which solved my problem. The startup penalty in the K8S stack was about 6 additional seconds