Sync documentation of main branch

Author: actions-user

_generated-doc/main/config/quarkus-all-config.adoc

@@ -34934,6 +34934,27 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`true`
 
+a| [[quarkus-jfr_quarkus-jfr-runtime-enabled]] [.property-path]##link:#quarkus-jfr_quarkus-jfr-runtime-enabled[`quarkus.jfr.runtime.enabled`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.jfr.runtime.enabled+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+If false, only Runtime events in quarkus-jfr are not recorded even if JFR is enabled. In this case, other quarkus-jfr, Java standard API and virtual machine information will be recorded according to the setting. Default value is `true`
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_JFR_RUNTIME_ENABLED+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_JFR_RUNTIME_ENABLED+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`true`
+
 
 h|[.extension-name]##JAXB##
 h|Type

_generated-doc/main/config/quarkus-jfr.adoc

@@ -49,5 +49,26 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`true`
 
+a| [[quarkus-jfr_quarkus-jfr-runtime-enabled]] [.property-path]##link:#quarkus-jfr_quarkus-jfr-runtime-enabled[`quarkus.jfr.runtime.enabled`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.jfr.runtime.enabled+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+If false, only Runtime events in quarkus-jfr are not recorded even if JFR is enabled. In this case, other quarkus-jfr, Java standard API and virtual machine information will be recorded according to the setting. Default value is `true`
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_JFR_RUNTIME_ENABLED+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_JFR_RUNTIME_ENABLED+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`true`
+
 |===
 

_generated-doc/main/config/quarkus-jfr_quarkus.jfr.adoc

@@ -49,5 +49,26 @@ endif::add-copy-button-to-env-var[]
 |boolean
 |`true`
 
+a| [[quarkus-jfr_quarkus-jfr-runtime-enabled]] [.property-path]##link:#quarkus-jfr_quarkus-jfr-runtime-enabled[`quarkus.jfr.runtime.enabled`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.jfr.runtime.enabled+++[]
+endif::add-copy-button-to-config-props[]
+
+
+[.description]
+--
+If false, only Runtime events in quarkus-jfr are not recorded even if JFR is enabled. In this case, other quarkus-jfr, Java standard API and virtual machine information will be recorded according to the setting. Default value is `true`
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_JFR_RUNTIME_ENABLED+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_JFR_RUNTIME_ENABLED+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`true`
+
 |===
 

_versions/main/guides/container-image.adoc

@@ -150,7 +150,7 @@ For example, building multi-platform images is implemented differently for Docke
 === OpenShift
 
 The extension `quarkus-container-image-openshift` is using OpenShift binary builds in order to perform container builds inside the OpenShift cluster.
-The idea behind the binary build is that you just upload the artifact and its dependencies to the cluster and during the build they will be merged to a builder image (defaults to `fabric8/s2i-java`).
+The idea behind the binary build is that you just upload the artifact and its dependencies to the cluster and during the build they will be merged to a builder image (defaults to `ubi9/openjdk-17` or `ubi9/openjdk-21`).
 
 The benefit of this approach, is that it can be combined with OpenShift's `DeploymentConfig` that makes it easy to roll out changes to the cluster.
 

_versions/main/guides/jfr.adoc

@@ -251,6 +251,22 @@ We can check if the Resource Method was executed as expected by the HTTP Method
 
 Client records information about the accessing client.
 
+=== Runtime Event
+This event is recorded by default.
+The following three JFR events are recorded in JFR chunks.
+
+QuarkusRuntime::
+
+  Records information about Quarkus running. This event includes the Quarkus version, its profiles, and the mode in which it is running.
+
+QuarkusApplication::
+
+  Records information about Quarkus application running. This event includes the name of the application and its version.
+
+Extension::
+
+  Records information about extensions included in the running Quarkus. This event includes the name of the extensions installed in Quarkus.
+
 === Native Image
 
 Native executables supports Java Flight Recorder.