From 8b876559d29622434459b79f4848542d423f404c Mon Sep 17 00:00:00 2001 From: Peter Zaoral Date: Tue, 24 Sep 2024 14:57:34 +0200 Subject: [PATCH] Operator's guides: Clarify that options need to be baked in the custom image to make the feature available Closes: #32717 Signed-off-by: Peter Zaoral --- docs/guides/operator/customizing-keycloak.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/guides/operator/customizing-keycloak.adoc b/docs/guides/operator/customizing-keycloak.adoc index 3f12b45b0469..4a63fad781f0 100644 --- a/docs/guides/operator/customizing-keycloak.adoc +++ b/docs/guides/operator/customizing-keycloak.adoc @@ -21,6 +21,7 @@ When using the default {project_name} image, the server will perform a costly re To avoid this delay, you can provide a custom image with the augmentation built-in from the build time of the image. With a custom image, you can also specify the Keycloak _build-time_ configurations and extensions during the build of the container. +Options like `health-enabled` and `metrics-enabled` are good examples of why this is sometimes necessary. By default, these options are disabled. To make these endpoints available, you can either use the `ENV` instruction in the Containerfile or specify them as parameters of the {project_name}'s `build` command. For instructions on how to build such an image, see <@links.server id="containers"/>.