Reviewed the affinity trait doc
@@ -120,15 +120,15 @@ $ kamel run -t affinity.node-affinity-labels="kubernetes.io/hostname in(node-66-
* To schedule a single integration pod per node (using the `Exists` operator):
[source,shell]
-$ kamel run -t affinity.node-anti-affinity-labels="camel.apache.org/integration" ...
+$ kamel run -t affinity.pod-anti-affinity-labels="camel.apache.org/integration" ...
* To co-locate the integration pod(s) with other integration pod(s):
[source,shell]
-$ kamel run -t affinity.node-affinity-labels="camel.apache.org/integration in(it1, it2)" ...
+$ kamel run -t affinity.pod-affinity-labels="camel.apache.org/integration in(it1, it2)" ...
The labels options follow the requirements from https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#label-selectors[Label selectors]. They can be multi-valuated, then the requirements list is ANDed, e.g., to schedule a single integration pod per node AND not co-located with the Camel K operator pod(s):
[source,shell]
-$ kamel run -t affinity.node-anti-affinity-labels="camel.apache.org/integration" -t affinity.node-anti-affinity-labels="camel.apache.org/component=operator" ...
+$ kamel run -t affinity.pod-anti-affinity-labels="camel.apache.org/integration" -t affinity.pod-anti-affinity-labels="camel.apache.org/component=operator" ...
More information can be found in the official Kubernetes documentation about https://kubernetes.io/docs/concepts/configuration/assign-pod-node/[Assigning Pods to Nodes].
