Knative Eventing provides an event model that connects Kubernetes workloads to external event systems—including GitHub, ApsaraMQ for RocketMQ, ApsaraMQ for Kafka, and Container Registry. Events are routed to Knative Services or functions using a broker and trigger model, enabling use cases such as AI audio and video processing, cron jobs, and automated container image builds on code commits.
How it works
Knative Eventing is built around three layers: event sources, event ingestion and subscription, and event filtering. Together, these layers form a serverless event-driven architecture.
| Layer | Description |
|---|---|
| Event sources | The Knative community provides event sources for systems such as Kafka and GitHub. You can also ingest events from message services like EventBridge. |
| Event processing | Brokers route events to event sinks or consumers. Create one or more triggers to filter events by attribute or subscribe to a specific event type. Events are consumed by serverless applications managed by Knative. |
| Event consumption | Typical patterns include releasing container images in Container Registry when a new image is pushed, building container images on code commits, running cron jobs, and processing AI audio and video workloads. |
What's next
-
Deploy Knative Eventing: Deploy Knative Eventing to install the component in your cluster.
-
Connect event sources: Use Knative to manage GitHub events and use Knative to manage MnsOss event sources for additional event-driven integrations.