This is an automated email from the ASF dual-hosted git repository.
bvahdat pushed a commit to branch typo
in repository https://gitbox.apache.org/repos/asf/camel-k.git
commit ba70ade4ca7db8e814ea8ccba2ec0a1ddbaa7696
Author: Babak Vahdat <bvah...@apache.org>
AuthorDate: Tue Feb 27 15:09:09 2024 +0100
update quarkus-native.adoc
---
docs/modules/ROOT/pages/running/quarkus-native.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/modules/ROOT/pages/running/quarkus-native.adoc
b/docs/modules/ROOT/pages/running/quarkus-native.adoc
index 323c210dd..a178d1afe 100644
--- a/docs/modules/ROOT/pages/running/quarkus-native.adoc
+++ b/docs/modules/ROOT/pages/running/quarkus-native.adoc
@@ -13,7 +13,7 @@ This is the default. As the default Camel K runtime is
Quarkus, then, every Came
If you want to go Quarkus native, then you need to familiarize with the
xref:traits:quarkus.adoc[Quarkus trait]. This trait is used to configure any
aspect related to Quarkus build. The most straightforward way is to use
`quarkus.build-mode=native` parameter:
[source,console]
-$ kamel run quarkus.build-mode=native ...
+$ kamel run -t quarkus.build-mode=native ...
This one will trigger a native compilation on your cluster. Mind that a native
compilation require quite certain amount of memory and specific tooling
(GraalVM). For this reason, any native build will be forced to execute with
`pod` build strategy, meaning that a new Kubernetes Pod is scheduled to perform
such operation. We calculate certain sensible values for Kubernetes resource
such as memory and CPU (4Gi and 1000 millicores). However, depending on the
complexity of your Camel applica [...]
