Start and Shutdown

The time it takes to start Keycloak is strongly influenced by the allowed CPU resources. Increasing the CPU limit makes Keycloak start faster by giving it a bigger share of CPU resources (or just more CPU in case there are excess resources).

The startup time of MACMA’s Keycloak image has been optimized for MSSQL and deployment with the context path '/iam' (see parameter KEYCLOAK_WEB_CONTEXT_PATH) to optimize for the Nexeed IAS cloud offering. Deviating from those defaults adds 5-20 seconds of startup time (depending on available computing resources) to adapt the container to the chosen settings.