An event source is an object that links an event producer with an event sink, or consumer. A sink can be a Knative service, channel, or broker that receives events from an event source.
Currently, OpenShift Serverless supports the following event source types:
Connects a sink to the Kubernetes API server.
Periodically sends ping events with a constant payload. It can be used as a timer.
Allows you to connect core Kubernetes resource objects such as a Deployment, Job, or StatefulSet with a sink.
Connect a Kafka cluster to a sink as an event source.
|
Apache Kafka on OpenShift Serverless is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/. |
You can create and manage Knative event sources using the Developer perspective in the OpenShift Container Platform web console, the kn CLI, or by applying YAML files.
Create an ApiServerSource.
Create an PingSource.
Create a SinkBinding.
Create a KafkaSource.
For more information about eventing workflows using OpenShift Serverless, see Knative Eventing architecture.
For more information about using Kafka event sources, see Using Apache Kafka with OpenShift Serverless.