Keycloak docker wait till all is up instead report ready state after just wildfly up on Cloud Run

Hi, I’m running Keycloak on GCP Cloud Run. I found out that because of under Keycloak itself there is Wilfdly which is starting first and reporting OK state it’s causing issues with scaling and starting new Revision on Cloud Run.

Often application is in ready state after everything is up and running but it’s also not using eg wildfly or anything similar but rather run application directly.

Is there a way either remove Wildfly or make wildfly not respond on requests on “/” and 8080 port untill everything is running?

Cloud Run does not have a readiness check other than confirming your service is listening on the specified port. Once that is done traffic starts routing to the new revision and previous serving revisions are scaled down as they wrap up in-progress requests.