You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any running Camel K Integration is associated to a shared IntegrationPlatform resource that contains general configuration options.
4
+
The integration platform is located in the operator namespace and typically uses the same name as the operator id that this platform belongs to.
5
+
6
+
Users may add an IntegrationProfile resource to any namespace. The profile holds custom settings which can be applied to all Integrations.
7
+
8
+
The profile must be explicitly selected by an annotation referencing the integration profile name (any resource belonging to the "camel.apache.org" group can select a particular profile configuration).
9
+
10
+
To specify which profile should be used for an Integration, the resource can be annotated like in the following example:
The value of the `camel.apache.org/integration-profile.id` annotation must match the name of an IntegrationProfile custom resource which is available in the same namespace of the Integration. Here an example of a profile:
23
+
24
+
[source,yaml]
25
+
----
26
+
kind: IntegrationProfile
27
+
apiVersion: camel.apache.org/v1
28
+
metadata:
29
+
name: my-profile
30
+
spec:
31
+
traits:
32
+
camel:
33
+
runtimeProvider: plain-quarkus
34
+
runtimeVersion: 3.30.8
35
+
owner:
36
+
targetLabels:
37
+
- camel.apache.org/app
38
+
...
39
+
# ...
40
+
----
41
+
42
+
The selection of a IntegrationProfile enables new configuration scenarios, for example, sharing global configuration options for groups of Integrations. The main configuration expected here is related to traits.
Copy file name to clipboardExpand all lines: docs/modules/ROOT/pages/installation/advanced/multi.adoc
-35Lines changed: 0 additions & 35 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,38 +54,3 @@ In order to install more than one operator globally, you may need to change the
54
54
```
55
55
cd /install/base/config/rbac/descoped && kustomize edit set namesuffix -- -$OPERATOR_ID
56
56
```
57
-
58
-
[[advanced-installation-integration-profile]]
59
-
== Apply custom IntegrationProfile settings
60
-
61
-
Any running Camel K integration is associated to a shared IntegrationPlatform resource that contains general configuration options.
62
-
The integration platform is located in the operator namespace and typically uses the same name as the operator id that this platform belongs to.
63
-
Each Camel K operator uses exactly one single integration platform in a "Ready" state.
64
-
IntegrationPlatform resources are somewhat "singleton" in a namespace and belong to a single operator instance.
65
-
66
-
There's a way to allow customizations regarding the integration configuration.
67
-
Users may add IntegrationProfile resources to an individual namespace.
68
-
The profile holds custom integration platform settings for them to be used by integrations.
69
-
The IntegrationProfile resource allows only a subset of the IntegrationPlatform settings for customization.
70
-
71
-
The custom IntegrationProfile resource uses the operator id as an annotation to bind its reconciliation to an operator instance.
72
-
Also, the profile must be explicitly selected by an annotation referencing the integration profile name (any resource belonging to the "camel.apache.org" group can select a particular profile configuration).
73
-
74
-
To specify which profile should be used for an integration, the resource can be annotated like in the following example:
The value of the `camel.apache.org/integration-profile.id` annotation must match the name of an IntegrationProfile custom resource.
87
-
The profile gets automatically resolved from the annotated resource namespace or from the operator namespace.
88
-
In case you need to explicitly set the integration profile namespace you can do so with the `camel.apache.org/integration-profile.namespace` annotation.
89
-
90
-
The selection of a IntegrationProfile enables new configuration scenarios, for example, sharing global configuration options for groups of integrations, or also
91
-
providing per-operator specific configuration options e.g. when you install multiple global operators in the cluster.
0 commit comments