Red Hat Camel K is deprecated
Red Hat Camel K is deprecated and the End of Life date for this product is June 30, 2025. For help migrating to the current go-to solution, Red Hat build of Apache Camel, see the Migration Guide.Chapter 70. Timer Source
Produces periodic events with a custom payload.
70.1. Configuration Options
The following table summarizes the configuration options available for the timer-source Kamelet:
| Property | Name | Description | Type | Default | Example |
|---|---|---|---|---|---|
| message * | Message | The message to generate | string |
| |
| contentType | Content Type | The content type of the message being generated | string |
| |
| period | Period | The interval between two events in milliseconds | integer |
| |
| repeatCount | Repeat Count | Specifies the maximum limit of the number of fires | integer |
Fields marked with an asterisk (*) are mandatory.
70.2. Dependencies
At runtime, the timer-source Kamelet relies upon the presence of the following dependencies:
- camel:core
- camel:timer
- camel:kamelet
70.3. Usage
This section describes how you can use the timer-source.
70.3.1. Knative Source
You can use the timer-source Kamelet as a Knative source by binding it to a Knative object.
timer-source-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: timer-source-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: timer-source
properties:
message: "hello world"
sink:
ref:
kind: Channel
apiVersion: messaging.knative.dev/v1
name: mychannel
70.3.1.1. Prerequisite
Make sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.
70.3.1.2. Procedure for using the cluster CLI
-
Save the
timer-source-binding.yamlfile to your local drive, and then edit it as needed for your configuration. Run the source by using the following command:
oc apply -f timer-source-binding.yaml
70.3.1.3. Procedure for using the Kamel CLI
Configure and run the source by using the following command:
kamel bind timer-source -p "source.message=hello world" channel:mychannel
This command creates the KameletBinding in the current namespace on the cluster.
70.3.2. Kafka Source
You can use the timer-source Kamelet as a Kafka source by binding it to a Kafka topic.
timer-source-binding.yaml
apiVersion: camel.apache.org/v1alpha1
kind: KameletBinding
metadata:
name: timer-source-binding
spec:
source:
ref:
kind: Kamelet
apiVersion: camel.apache.org/v1alpha1
name: timer-source
properties:
message: "hello world"
sink:
ref:
kind: KafkaTopic
apiVersion: kafka.strimzi.io/v1beta1
name: my-topic
70.3.2.1. Prerequisites
Ensure that you’ve installed the AMQ Streams operator in your OpenShift cluster and created a topic named my-topic in the current namespace. Make also sure you have "Red Hat Integration - Camel K" installed into the OpenShift cluster you’re connected to.
70.3.2.2. Procedure for using the cluster CLI
-
Save the
timer-source-binding.yamlfile to your local drive, and then edit it as needed for your configuration. Run the source by using the following command:
oc apply -f timer-source-binding.yaml
70.3.2.3. Procedure for using the Kamel CLI
Configure and run the source by using the following command:
kamel bind timer-source -p "source.message=hello world" kafka.strimzi.io/v1beta1:KafkaTopic:my-topic
This command creates the KameletBinding in the current namespace on the cluster.
70.4. Kamelet source file
https://github.com/openshift-integration/kamelet-catalog/timer-source.kamelet.yaml
