LDAP configuration is not active after startup

Hi,

I am running Keycloak 19.03 in Kubernetes and have LDAP provider specified in my custom realm.
It works fine so far but when I make a new deployment or restart a keycloak pod the LDAP configuration is not active automatically after the Keycloak instance is started and needs a first hit of user credentials to start looking there. Basically I click on “Login” in my app, get an error saying “bad credentials”. In logs it is saying then: “Creating new LDAP Store for the LDAP storage provider …” and only after this message on a second try I am able to login successfully.

How to force Keycloak to add/use LDAP directly after its startup?