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 d888219f4 doc(trait): sourceless Integrations
d888219f4 is described below

commit d888219f44e08a982e226c8f5805a730380226bf
Author: Pasquale Congiusti <[email protected]>
AuthorDate: Thu Mar 21 10:46:13 2024 +0100

    doc(trait): sourceless Integrations
---
 .../modules/ROOT/pages/running/camel-runtimes.adoc | 262 +++++++++++++++++++++
 1 file changed, 262 insertions(+)

diff --git a/docs/modules/ROOT/pages/running/camel-runtimes.adoc 
b/docs/modules/ROOT/pages/running/camel-runtimes.adoc
index 393e69e0d..db1fdb235 100644
--- a/docs/modules/ROOT/pages/running/camel-runtimes.adoc
+++ b/docs/modules/ROOT/pages/running/camel-runtimes.adoc
@@ -20,3 +20,265 @@ At this stage we do have a container image with our Camel 
application. We can us
 NOTE: Jvm trait won't be available when running an application built 
externally.
 
 If all is good, in a few seconds (there is no build involved) you should have 
your application up and running and you can monitor and operate with Camel K as 
usual.
+
+[[traits-and-dependencies]]
+== Traits and dependencies
+
+Certain Camel K operational aspect may be driven by traits. When you're 
building the application outside the operator, some of those traits may not be 
executed as they are executed during the building phase that we are skipping 
when running **sourceless Integrations**. Here we provided a list of those 
traits that may not work when building the application outside the Camel K 
operator.
+
+NOTE: this is a best effort analysis taking as reference the work available in 
version 2.3.
+
+* Build column show those traits that affects the build (will be skipped for 
sourceless Integrations).
+* Dependencies column show those traits that will add some dependency (you may 
need to manually add those dependencies).
+* Runtime column show those traits that will influence the runtime, mostly via 
properties (you may need to manually add those properties to the bundled 
`application.properties`).
+* Deployment column show those traits that will be executed for the deployment 
(nothing should be required).
+
+[cols="1,1,1,1,1"]
+|===
+|Trait
+|Build
+|Dependencies
+|Runtime
+|Deployment
+
+|Affinity
+|x
+|x
+|x
+|v
+
+|Builder
+|v
+|x
+|x
+|x
+
+|Camel
+|x
+|x
+|v
+|x
+
+|Container
+|x
+|x
+|x
+|v
+
+|Cron
+|x
+|v
+|v
+|x
+
+|Dependencies
+|v
+|v
+|x
+|x
+
+|Deployer
+|x
+|x
+|x
+|v
+
+|Deployment
+|x
+|x
+|x
+|v
+
+|Environment
+|x
+|x
+|x
+|v
+
+|Affinity
+|x
+|x
+|x
+|v
+
+|Error Handler
+|x
+|v
+|x
+|x
+
+|GC (Garbage Collector)
+|x
+|x
+|x
+|v
+
+|Health
+|x
+|v
+|v
+|v
+
+|Ingress
+|x
+|x
+|x
+|v
+
+|Istio
+|x
+|x
+|x
+|v
+
+|Jolokia
+|x
+|v
+|v
+|v
+
+|JVM
+|x
+|x
+|v
+|v
+
+|Kamelets
+|x
+|x
+|v
+|x
+
+|KNative Service
+|v
+|x
+|x
+|x
+
+|KNative
+|x
+|v
+|x
+|x
+
+|Logging
+|x
+|x
+|v
+|v
+
+|Mount
+|x
+|x
+|x
+|v
+
+|Openapi
+|x
+|v
+|v
+|v
+
+|Owner
+|x
+|x
+|x
+|v
+
+|PDB
+|x
+|x
+|x
+|v
+
+|Platform
+|x
+|x
+|x
+|v
+
+|Pod
+|x
+|x
+|x
+|v
+
+|Prometheus
+|v
+|v
+|x
+|x
+
+|Pull Secret
+|x
+|x
+|x
+|v
+
+|Quarkus
+|v
+|x
+|x
+|x
+
+|Service
+|x
+|x
+|x
+|v
+
+|Service Binding
+|x
+|x
+|v
+|v
+
+|Toleration
+|x
+|x
+|x
+|v
+
+|Keda
+|x
+|x
+|x
+|v
+
+|Master
+|v
+|v
+|v
+|x
+
+|Resume
+|v
+|v
+|x
+|x
+
+|Strimzi
+|x
+|x
+|x
+|v
+
+|Telemetry
+|x
+|x
+|v
+|x
+
+|Three Scale
+|x
+|x
+|x
+|v
+
+|Vaults
+|x
+|v
+|v
+|x
+
+|===

Reply via email to