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
The following commit(s) were added to refs/heads/main by this push:
new 8c8161049 chore(doc): note about runtimes availability
8c8161049 is described below
commit 8c816104931164105539e2dc5aba185f89d9e48e
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Sat Sep 13 10:19:25 2025 +0200
chore(doc): note about runtimes availability
---
docs/modules/ROOT/pages/concepts/dependencies.adoc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/concepts/dependencies.adoc
b/docs/modules/ROOT/pages/concepts/dependencies.adoc
index 66c9f941b..61ad44ede 100644
--- a/docs/modules/ROOT/pages/concepts/dependencies.adoc
+++ b/docs/modules/ROOT/pages/concepts/dependencies.adoc
@@ -1,6 +1,8 @@
= Camel dependencies matrix
-From Camel K version 2 onward you will be able to use any Camel K Runtime.
Each runtime depends on a Camel Quarkus, Camel and Quarkus Platform version.
Every Camel K has a default runtime used, but you can
xref:configuration/runtime-version.adoc[pick any Camel K Runtime available]
(backward and forward compatible).
+Camel K was originally equipped with a dedicated runtime known as Camel K
Runtime. This is a lightweight layer on top of Camel Quarkus. However, you can
directly run plain regular Camel Quarkus runtime applications as well. This
will become the standard only from version 3.x onward in order to avoid
breaking backward compatibility. In the while you're strongly encouraged to use
`plain-quarkus` Camel runtime configuration to ease any future 3.x migration.
+
+NOTE: you can use any available Camel Quarkus runtime version. Alternatively
you can also build any other Camel runtimes building from a Git hosted
repository.
[caption=]
.Camel dependencies matrix
