Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 72. Kubernetes Event
Since Camel 3.20
Both producer and consumer are supported
The Kubernetes Event component is one of the Kubernetes Components which provides a producer to execute Kubernetes Event operations and a consumer to consume events related to Event objects.
72.1. Dependencies
When using kubernetes-events with Red Hat build of Apache Camel for Spring Boot, use the following Maven dependency to have support for auto configuration:
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-kubernetes-starter</artifactId> </dependency>
72.2. Configuring Options
Camel components are configured on two separate levels:
- component level
- endpoint level
72.2.1. Configuring Component Options
The component level is the highest level which holds general and common configurations that are inherited by the endpoints. For example a component may have security settings, credentials for authentication, urls for network connection and so forth.
Some components only have a few options, and others may have many. Because components typically have pre configured defaults that are commonly used, then you may often only need to configure a few options on a component; or none at all.
Configuring components can be done with the Component DSL, in a configuration file (application.properties|yaml), or directly with Java code.
72.2.2. Configuring Endpoint Options
Where you find yourself configuring the most is on endpoints, as endpoints often have many options, which allows you to configure what you need the endpoint to do. The options are also categorized into whether the endpoint is used as consumer (from) or as a producer (to), or used for both.
Configuring endpoints is most often done directly in the endpoint URI as path and query parameters. You can also use the Endpoint DSL as a type safe way of configuring endpoints.
A good practice when configuring options is to use Property Placeholders, which allows to not hardcode urls, port numbers, sensitive information, and other settings. In other words placeholders allows to externalize the configuration from your code, and gives more flexibility and reuse.
The following two sections lists all the options, firstly for the component followed by the endpoint.
72.3. Component Options
The Kubernetes Event component supports 4 options, which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
| kubernetesClient (common) | Autowired To use an existing kubernetes client. | KubernetesClient | |
| 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 |
72.4. Endpoint Options
The Kubernetes Event endpoint is configured using URI syntax:
kubernetes-events:masterUrl
with the following path and query parameters:
72.4.1. Path Parameters (1 parameters)
| Name | Description | Default | Type |
|---|---|---|---|
| masterUrl (common) | Required Kubernetes Master url. | String |
72.4.2. 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 | |
| namespace (common) | The namespace. | String | |
| portName (common) | The port name, used for ServiceCall EIP. | String | |
| portProtocol (common) | The port protocol, used for ServiceCall EIP. | tcp | String |
| 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 | |
| poolSize (consumer) | The Consumer pool size. | 1 | int |
| resourceName (consumer) | The Consumer Resource Name we would like to watch. | String | |
| bridgeErrorHandler (consumer (advanced)) | 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 |
| exceptionHandler (consumer (advanced)) | 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 (advanced)) | Sets the exchange pattern when the consumer creates an exchange. Enum values:
| ExchangePattern | |
| operation (producer) | Producer operation to do on Kubernetes. | String | |
| lazyStartProducer (producer (advanced)) | 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 |
| 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 |
72.5. Message Headers
The Kubernetes Event component supports 14 message header(s), which is/are listed below:
| Name | Description | Default | Type |
|---|---|---|---|
| CamelKubernetesOperation (producer) Constant: KUBERNETES_OPERATION | The Producer operation. | String | |
| CamelKubernetesNamespaceName (producer) Constant: KUBERNETES_NAMESPACE_NAME | The namespace name. | String | |
| CamelKubernetesEventsLabels (producer) Constant: KUBERNETES_EVENTS_LABELS | The event labels. | Map | |
| CamelKubernetesEventTime (producer) Constant: KUBERNETES_EVENT_TIME | The event time in ISO-8601 extended offset date-time format, such as '2011-12-03T10:15:3001:00'. | server time | String |
| CamelKubernetesEventAction (consumer) Constant: KUBERNETES_EVENT_ACTION | Action watched by the consumer. Enum values:
| Action | |
| CamelKubernetesEventType (producer) Constant: KUBERNETES_EVENT_TYPE | The event type. | String | |
| CamelKubernetesEventReason (producer) Constant: KUBERNETES_EVENT_REASON | The event reason. | String | |
| CamelKubernetesEventNote (producer) Constant: KUBERNETES_EVENT_NOTE | The event note. | String | |
| CamelKubernetesEventRegarding (producer) Constant: KUBERNETES_EVENT_REGARDING | The event regarding. | ObjectReference | |
| CamelKubernetesEventRelated (producer) Constant: KUBERNETES_EVENT_RELATED | The event related. | ObjectReference | |
| CamelKubernetesEventReportingController (producer) Constant: KUBERNETES_EVENT_REPORTING_CONTROLLER | The event reporting controller. | String | |
| CamelKubernetesEventReportingInstance (producer) Constant: KUBERNETES_EVENT_REPORTING_INSTANCE | The event reporting instance. | String | |
| CamelKubernetesEventName (producer) Constant: KUBERNETES_EVENT_NAME | The event name. | String | |
| CamelKubernetesEventTimestamp (consumer) Constant: KUBERNETES_EVENT_TIMESTAMP | Timestamp of the action watched by the consumer. | long |
72.6. Supported producer operation
- listEvents
- listEventsByLabels
- getEvent
- createEvent
- updateEvent
- deleteEvent
72.7. Kubernetes Events Producer Examples
- listEvents: this operation lists the events.
from("direct:list").
to("kubernetes-events:///?kubernetesClient=#kubernetesClient&operation=listEvents").
to("mock:result");
This operation returns a list of events from your cluster. The type of the events is io.fabric8.kubernetes.api.model.events.v1.Event.
To indicate from which namespace the events are expected, it is possible to set the message header CamelKubernetesNamespaceName. By default, the events of all namespaces are returned.
- listEventsByLabels: this operation lists the events selected by labels.
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_EVENTS_LABELS, labels);
}
});
to("kubernetes-events:///?kubernetesClient=#kubernetesClient&operation=listEventsByLabels").
to("mock:result");
This operation returns a list of events from your cluster that occurred in any namespaces, using a label selector (in the example above only expect events which have the label "key1" set to "value1" and the label "key2" set to "value2"). The type of the events is io.fabric8.kubernetes.api.model.events.v1.Event.
This operation expects the message header CamelKubernetesEventsLabels to be set to a Map<String, String> where the key-value pairs represent the expected label names and values.
- getEvent: this operation gives a specific event.
from("direct:get").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_NAMESPACE_NAME, "test");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_EVENT_NAME, "event1");
}
});
to("kubernetes-events:///?kubernetesClient=#kubernetesClient&operation=getEvent").
to("mock:result");
This operation returns the event matching the criteria from your cluster. The type of the event is io.fabric8.kubernetes.api.model.events.v1.Event.
This operation expects two message headers which are CamelKubernetesNamespaceName and CamelKubernetesEventName, the first one needs to be set to the name of the target namespace and second one needs to be set to the target name of event.
If no matching event could be found, null is returned.
- createEvent: this operation creates a new event.
from("direct:get").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_NAMESPACE_NAME, "default");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_EVENT_NAME, "test1");
Map<String, String> labels = new HashMap<>();
labels.put("this", "rocks");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_EVENTS_LABELS, labels);
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_EVENT_ACTION_PRODUCER, "Some Action");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_EVENT_TYPE, "Normal");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_EVENT_REASON, "Some Reason");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_EVENT_REPORTING_CONTROLLER, "Some-Reporting-Controller");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_EVENT_REPORTING_INSTANCE, "Some-Reporting-Instance");
}
});
to("kubernetes-events:///?kubernetesClient=#kubernetesClient&operation=createEvent").
to("mock:result");
This operation publishes a new event in your cluster. An event can be created in two ways either from message headers or directly from an io.fabric8.kubernetes.api.model.events.v1.EventBuilder.
Whatever the way used to create the event:
-
The operation expects two message headers which are
CamelKubernetesNamespaceNameandCamelKubernetesEventName, to set respectively the name of namespace and the name of the produced event. -
The operation supports the message header
CamelKubernetesEventsLabelsto set the labels to the produced event.
The message headers that can be used to create an event are CamelKubernetesEventTime, CamelKubernetesEventAction, CamelKubernetesEventType, CamelKubernetesEventReason, CamelKubernetesEventNote,CamelKubernetesEventRegarding, CamelKubernetesEventRelated, CamelKubernetesEventReportingController and CamelKubernetesEventReportingInstance.
In case the supported message headers are not enough for a specific use case, it is still possible to set the message body with an object of type io.fabric8.kubernetes.api.model.events.v1.EventBuilder representing a prefilled builder to use when creating the event. Please note that the labels, name of event and name of namespace are always set from the message headers, even when the builder is provided.
- updateEvent: this operation updates an existing event.
The behavior is exactly the same as createEvent, only the name of the operation is different.
- deleteEvent: this operation deletes an existing event.
from("direct:get").process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception {
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_NAMESPACE_NAME, "default");
exchange.getIn().setHeader(KubernetesConstants.KUBERNETES_EVENT_NAME, "test1");
}
});
to("kubernetes-events:///?kubernetesClient=#kubernetesClient&operation=deleteEvent").
to("mock:result");
This operation removes an existing event from your cluster. It returns a boolean to indicate whether the operation was successful or not.
This operation expects two message headers which are CamelKubernetesNamespaceName and CamelKubernetesEventName, the first one needs to be set to the name of the target namespace and second one needs to be set to the target name of event.
72.8. Kubernetes Events Consumer Example
fromF("kubernetes-events://%s?oauthToken=%s", host, authToken)
.setHeader(KubernetesConstants.KUBERNETES_NAMESPACE_NAME, constant("default"))
.setHeader(KubernetesConstants.KUBERNETES_EVENT_NAME, constant("test"))
.process(new KubernertesProcessor()).to("mock:result");
public class KubernertesProcessor implements Processor {
@Override
public void process(Exchange exchange) throws Exception {
Message in = exchange.getIn();
Event cm = exchange.getIn().getBody(Event.class);
log.info("Got event with event name: " + cm.getMetadata().getName() + " and action " + in.getHeader(KubernetesConstants.KUBERNETES_EVENT_ACTION));
}
}
This consumer returns a message per event received on the namespace "default" for the event "test". It also set the action (io.fabric8.kubernetes.client.Watcher.Action) in the message header CamelKubernetesEventAction and the timestamp (long) in the message header CamelKubernetesEventTimestamp.
72.9. Spring Boot Auto-Configuration
The component supports 102 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.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-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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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-events.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-events.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-events.enabled | Whether to enable auto configuration of the kubernetes-events component. This is enabled by default. | Boolean | |
| camel.component.kubernetes-events.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| camel.component.kubernetes-events.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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| 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 |
| camel.component.openshift-deploymentconfigs.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-deploymentconfigs.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.openshift-deploymentconfigs.enabled | Whether to enable auto configuration of the openshift-deploymentconfigs component. This is enabled by default. | Boolean | |
| camel.component.openshift-deploymentconfigs.kubernetes-client | To use an existing kubernetes client. The option is a io.fabric8.kubernetes.client.KubernetesClient type. | KubernetesClient | |
| camel.component.openshift-deploymentconfigs.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 |
