Kubernetes Job
Since Camel 2.23
Both producer and consumer are supported
The Kubernetes Job component is one of Kubernetes Components which provides a producer to execute kubernetes Job operations and a consumer to consume events related to Job objects.
Component Options
The Kubernetes Job component supports 3 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
bridgeErrorHandler (consumer) |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
boolean |
lazyStartProducer (producer) |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
autowiredEnabled (advanced) |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
boolean |
Endpoint Options
The Kubernetes Job endpoint is configured using URI syntax:
kubernetes-job:masterUrl
with the following path and query parameters:
Path Parameters (1 parameters):
Name | Description | Default | Type |
---|---|---|---|
masterUrl |
Required Kubernetes Master url |
String |
Query Parameters (33 parameters):
Name | Description | Default | Type |
---|---|---|---|
apiVersion (common) |
The Kubernetes API Version to use |
String |
|
dnsDomain (common) |
The dns domain, used for ServiceCall EIP |
String |
|
kubernetesClient (common) |
Default KubernetesClient to use if provided |
KubernetesClient |
|
portName (common) |
The port name, used for ServiceCall EIP |
String |
|
portProtocol (common) |
The port protocol, used for ServiceCall EIP |
tcp |
String |
bridgeErrorHandler (consumer) |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
boolean |
crdGroup (consumer) |
The Consumer CRD Resource Group we would like to watch |
String |
|
crdName (consumer) |
The Consumer CRD Resource name we would like to watch |
String |
|
crdPlural (consumer) |
The Consumer CRD Resource Plural we would like to watch |
String |
|
crdScope (consumer) |
The Consumer CRD Resource Scope we would like to watch |
String |
|
crdVersion (consumer) |
The Consumer CRD Resource Version we would like to watch |
String |
|
labelKey (consumer) |
The Consumer Label key when watching at some resources |
String |
|
labelValue (consumer) |
The Consumer Label value when watching at some resources |
String |
|
namespace (consumer) |
The namespace |
String |
|
poolSize (consumer) |
The Consumer pool size |
1 |
int |
resourceName (consumer) |
The Consumer Resource Name we would like to watch |
String |
|
exceptionHandler (consumer) |
To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
ExceptionHandler |
|
exchangePattern (consumer) |
Sets the exchange pattern when the consumer creates an exchange. There are 3 enums and the value can be one of: InOnly, InOut, InOptionalOut |
ExchangePattern |
|
lazyStartProducer (producer) |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
boolean |
operation (producer) |
Producer operation to do on Kubernetes |
String |
|
connectionTimeout (advanced) |
Connection timeout in milliseconds to use when making requests to the Kubernetes API server. |
Integer |
|
caCertData (security) |
The CA Cert Data |
String |
|
caCertFile (security) |
The CA Cert File |
String |
|
clientCertData (security) |
The Client Cert Data |
String |
|
clientCertFile (security) |
The Client Cert File |
String |
|
clientKeyAlgo (security) |
The Key Algorithm used by the client |
String |
|
clientKeyData (security) |
The Client Key data |
String |
|
clientKeyFile (security) |
The Client Key file |
String |
|
clientKeyPassphrase (security) |
The Client Key Passphrase |
String |
|
oauthToken (security) |
The Auth Token |
String |
|
password (security) |
Password to connect to Kubernetes |
String |
|
trustCerts (security) |
Define if the certs we used are trusted anyway or not |
Boolean |
|
username (security) |
Username to connect to Kubernetes |
String |
Kubernetes Job Producer Examples
-
listJob: this operation list the jobs on a kubernetes cluster
from("direct:list").
toF("kubernetes-job:///?kubernetesClient=#kubernetesClient&operation=listJob").
to("mock:result");
This operation return a List of Job from your cluster
-
listJobByLabels: this operation list the jobs by labels on a kubernetes cluster
from("direct:listByLabels").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
Map<String, String> labels = new HashMap<>();
labels.put("key1", "value1");
labels.put("key2", "value2");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_JOB_LABELS, labels);
}
});
toF("kubernetes-job:///?kubernetesClient=#kubernetesClient&operation=listJobByLabels").
to("mock:result");
This operation return a List of Jobs from your cluster, using a label selector (with key1 and key2, with value value1 and value2)
-
createJob: This operation create a job on a Kubernetes Cluster
We have a wonderful example of this operation thanks to Emmerson Miranda from this Java test
import java.util.ArrayList;
import java.util.Date;
import java.util.HashMap;
import java.util.List;
import java.util.Map;
import javax.inject.Inject;
import org.apache.camel.Endpoint;
import org.apache.camel.builder.RouteBuilder;
import org.apache.camel.cdi.Uri;
import org.apache.camel.component.kubernetes.KubernetesConstants;
import org.apache.camel.component.kubernetes.KubernetesOperations;
import io.fabric8.kubernetes.api.model.Container;
import io.fabric8.kubernetes.api.model.ObjectMeta;
import io.fabric8.kubernetes.api.model.PodSpec;
import io.fabric8.kubernetes.api.model.PodTemplateSpec;
import io.fabric8.kubernetes.api.model.batch.JobSpec;
/**
*
*/
public class KubernetesCreateJob extends RouteBuilder {
@Inject
@Uri("timer:foo?delay=1000&repeatCount=1")
private Endpoint inputEndpoint;
@Inject
@Uri("log:output")
private Endpoint resultEndpoint;
@Override
public void configure() {
// you can configure the route rule with Java DSL here
from(inputEndpoint)
.routeId("kubernetes-jobcreate-client")
.process(exchange -> {
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_JOB_NAME, "camel-job"); //DNS-1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_NAMESPACE_NAME, "default");
Map<String, String> joblabels = new HashMap<String, String>();
joblabels.put("jobLabelKey1", "value1");
joblabels.put("jobLabelKey2", "value2");
joblabels.put("app", "jobFromCamelApp");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_JOB_LABELS, joblabels);
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_JOB_SPEC, generateJobSpec());
})
.toF("kubernetes-job:///{{kubernetes-master-url}}?oauthToken={{kubernetes-oauth-token:}}&operation=" + KubernetesOperations.CREATE_JOB_OPERATION)
.log("Job created:")
.process(exchange -> {
System.out.println(exchange.getIn().getBody());
})
.to(resultEndpoint);
}
/**
* Create a new JobSpec
* @return
*/
private JobSpec generateJobSpec() {
JobSpec js = new JobSpec();
PodTemplateSpec pts = new PodTemplateSpec();
PodSpec ps = new PodSpec();
ps.setRestartPolicy("Never");
ps.setContainers(generateContainers());
pts.setSpec(ps);
ObjectMeta metadata = new ObjectMeta();
Map<String, String> annotations = new HashMap<String, String>();
annotations.put("jobMetadataAnnotation1", "random value");
metadata.setAnnotations(annotations);
Map<String, String> podlabels = new HashMap<String, String>();
podlabels.put("podLabelKey1", "value1");
podlabels.put("podLabelKey2", "value2");
podlabels.put("app", "podFromCamelApp");
metadata.setLabels(podlabels);
pts.setMetadata(metadata);
js.setTemplate(pts);
return js;
}
private List<Container> generateContainers() {
Container container = new Container();
container.setName("pi");
container.setImage("perl");
List<String> command = new ArrayList<String>();
command.add("echo");
command.add("Job created from Apache Camel code at " + (new Date()));
container.setCommand(command);
List<Container> containers = new ArrayList<Container>();
containers.add(container);
return containers;
}
}
Spring Boot Auto-Configuration
When using kubernetes with Spring Boot make sure to use the following Maven dependency to have support for auto configuration:
<dependency>
<groupId>org.apache.camel.springboot</groupId>
<artifactId>camel-kubernetes-starter</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>
The component supports 74 options, which are listed below.
Name | Description | Default | Type |
---|---|---|---|
camel.cluster.kubernetes.attributes |
Custom service attributes. |
Map |
|
camel.cluster.kubernetes.cluster-labels |
Set the labels used to identify the pods composing the cluster. |
Map |
|
camel.cluster.kubernetes.config-map-name |
Set the name of the ConfigMap used to do optimistic locking (defaults to 'leaders'). |
String |
|
camel.cluster.kubernetes.connection-timeout-millis |
Connection timeout in milliseconds to use when making requests to the Kubernetes API server. |
Integer |
|
camel.cluster.kubernetes.enabled |
Sets if the Kubernetes cluster service should be enabled or not, default is false. |
false |
Boolean |
camel.cluster.kubernetes.id |
Cluster Service ID |
String |
|
camel.cluster.kubernetes.jitter-factor |
A jitter factor to apply in order to prevent all pods to call Kubernetes APIs in the same instant. |
Double |
|
camel.cluster.kubernetes.kubernetes-namespace |
Set the name of the Kubernetes namespace containing the pods and the configmap (autodetected by default) |
String |
|
camel.cluster.kubernetes.lease-duration-millis |
The default duration of the lease for the current leader. |
Long |
|
camel.cluster.kubernetes.master-url |
Set the URL of the Kubernetes master (read from Kubernetes client properties by default). |
String |
|
camel.cluster.kubernetes.order |
Service lookup order/priority. |
Integer |
|
camel.cluster.kubernetes.pod-name |
Set the name of the current pod (autodetected from container host name by default). |
String |
|
camel.cluster.kubernetes.renew-deadline-millis |
The deadline after which the leader must stop its services because it may have lost the leadership. |
Long |
|
camel.cluster.kubernetes.retry-period-millis |
The time between two subsequent attempts to check and acquire the leadership. It is randomized using the jitter factor. |
Long |
|
camel.component.kubernetes-config-maps.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-config-maps.enabled |
Whether to enable auto configuration of the kubernetes-config-maps component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-config-maps.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-custom-resources.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-custom-resources.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.kubernetes-custom-resources.enabled |
Whether to enable auto configuration of the kubernetes-custom-resources component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-custom-resources.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-deployments.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-deployments.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.kubernetes-deployments.enabled |
Whether to enable auto configuration of the kubernetes-deployments component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-deployments.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-hpa.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-hpa.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.kubernetes-hpa.enabled |
Whether to enable auto configuration of the kubernetes-hpa component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-hpa.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-job.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-job.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.kubernetes-job.enabled |
Whether to enable auto configuration of the kubernetes-job component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-job.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-namespaces.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-namespaces.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.kubernetes-namespaces.enabled |
Whether to enable auto configuration of the kubernetes-namespaces component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-namespaces.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-nodes.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-nodes.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.kubernetes-nodes.enabled |
Whether to enable auto configuration of the kubernetes-nodes component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-nodes.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-persistent-volumes-claims.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-persistent-volumes-claims.enabled |
Whether to enable auto configuration of the kubernetes-persistent-volumes-claims component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-persistent-volumes-claims.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-persistent-volumes.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-persistent-volumes.enabled |
Whether to enable auto configuration of the kubernetes-persistent-volumes component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-persistent-volumes.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-pods.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-pods.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.kubernetes-pods.enabled |
Whether to enable auto configuration of the kubernetes-pods component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-pods.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-replication-controllers.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-replication-controllers.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.kubernetes-replication-controllers.enabled |
Whether to enable auto configuration of the kubernetes-replication-controllers component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-replication-controllers.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-resources-quota.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-resources-quota.enabled |
Whether to enable auto configuration of the kubernetes-resources-quota component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-resources-quota.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-secrets.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-secrets.enabled |
Whether to enable auto configuration of the kubernetes-secrets component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-secrets.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-service-accounts.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-service-accounts.enabled |
Whether to enable auto configuration of the kubernetes-service-accounts component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-service-accounts.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.kubernetes-services.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.kubernetes-services.bridge-error-handler |
Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. |
false |
Boolean |
camel.component.kubernetes-services.enabled |
Whether to enable auto configuration of the kubernetes-services component. This is enabled by default. |
Boolean |
|
camel.component.kubernetes-services.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.openshift-build-configs.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.openshift-build-configs.enabled |
Whether to enable auto configuration of the openshift-build-configs component. This is enabled by default. |
Boolean |
|
camel.component.openshift-build-configs.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |
camel.component.openshift-builds.autowired-enabled |
Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. |
true |
Boolean |
camel.component.openshift-builds.enabled |
Whether to enable auto configuration of the openshift-builds component. This is enabled by default. |
Boolean |
|
camel.component.openshift-builds.lazy-start-producer |
Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel’s routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. |
false |
Boolean |