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 1eb705275 chore(doc): remove runtime limitation
1eb705275 is described below
commit 1eb705275b6904254f91c97086e6e75aa5a59fde
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Fri Oct 10 12:40:35 2025 +0200
chore(doc): remove runtime limitation
---
docs/modules/ROOT/pages/running/self-managed.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/running/self-managed.adoc
b/docs/modules/ROOT/pages/running/self-managed.adoc
index 841c8ed3b..2a964d951 100644
--- a/docs/modules/ROOT/pages/running/self-managed.adoc
+++ b/docs/modules/ROOT/pages/running/self-managed.adoc
@@ -1,6 +1,6 @@
= Self Managed Build Integrations
-Camel K operator is traditionally in charge to perform a build from a Camel
DSL source. The resulting Integration depends directly on an
xref:architecture/cr/integration-kit.adoc[IntegrationKit], which is a reusable
custom resource backing the final container image that your application will
run. The only runtime the operator can build is Camel Quarkus (via Camel K
Runtime project).
+Camel K operator is traditionally in charge to perform a build from a Camel
DSL source. The resulting Integration depends directly on an
xref:architecture/cr/integration-kit.adoc[IntegrationKit], which is a reusable
custom resource backing the final container image that your application will
run.
However Camel K can run any runtime available in Apache Camel. This is
possible only when the Camel application was previously built and packaged into
a container image externally. Mind that if you run through this option, some of
the features offered by the operator may not be available. For example, you
won't be able to discover Camel capabilities because the source is not
available to the operator but embedded in the container image.
