(camel-k) 02/04: doc: base image explained

[pc...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

pcongiusti pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel-k.git

commit eb2f9c702f0d5158afd731b2ade17874b0df64d8
Author: Pasquale Congiusti <pa...@gmail.com>
AuthorDate: Thu May 23 12:18:40 2024 +0200

    doc: base image explained
---
 docs/modules/ROOT/pages/configuration/base-image.adoc | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/docs/modules/ROOT/pages/configuration/base-image.adoc b/docs/modules/ROOT/pages/configuration/base-image.adoc
new file mode 100644
index 000000000..55326d4c5
--- /dev/null
+++ b/docs/modules/ROOT/pages/configuration/base-image.adoc
@@ -0,0 +1,13 @@
+= Base image
+
+Camel K operator builds and containerize a Camel application in order to run it eventually on the cluster. It uses a base image on top of which it copies the Camel runtime dependencies built from the given source. The default image used is a JDK based image as the Java DSL requires a runtime compilation on the fly.
+
+You can change the base image in order to bring your own base image by changing the `.spec.build.baseImage` of your IntegrationPlatform resource.
+
+You can also change this parameter individually for each Integration you're running by overriding the platform default value with `builder.base-image` trait parameter.
+
+NOTE: if you change the base image, make sure it provides a JDK or a JRE (only if you are sure you don't use Java DSL)
+
+== "Distroless" container base images
+
+The classic container images such as Eclipse Temurin JDK (the one we use as a default base image at the time of writing this documentation) contains several tools that may not be very suitable for production environments. For this reason you can use a "distroless" container image which only contains the essential and is more secure and suitable for a production environment.