3ad1d9a853
* feat: restructure docs to match new navigation Signed-off-by: Calum Murray <cmurray@redhat.com> * fix: faq link is correct Signed-off-by: Calum Murray <cmurray@redhat.com> --------- Signed-off-by: Calum Murray <cmurray@redhat.com> |
||
|---|---|---|
| .. | ||
| brokers | ||
| channels | ||
| configuration | ||
| custom-event-source | ||
| data | ||
| experimental-features | ||
| faq | ||
| flows | ||
| images | ||
| observability | ||
| reference | ||
| sinks | ||
| sources | ||
| sugar | ||
| triggers | ||
| troubleshooting | ||
| OWNERS | ||
| README.md | ||
| accessing-traces.md | ||
| event-delivery.md | ||
| event-mesh.md | ||
| event-registry.md | ||
README.md
Knative Eventing - The Event-driven application platform for Kubernetes
--8<-- "about-eventing.md"
Examples of supported Knative Eventing use cases:
-
Publish an event without creating a consumer. You can send events to a broker as an HTTP POST, and use binding to decouple the destination configuration from your application that produces events.
-
Consume an event without creating a publisher. You can use a trigger to consume events from a broker based on event attributes. The application receives events as an HTTP POST.
!!! tip Multiple event producers and sinks can be used together to create more advanced Knative Eventing flows{target=_blank} to solve complex use cases.
Eventing examples
:material-file-document: Creating and responding to Kubernetes API events{target=blank}
--8<-- "YouTube_icon.svg" Creating an image processing pipeline{target=blank}
--8<-- "YouTube_icon.svg" Facilitating AI workloads at the edge in large-scale, drone-powered sustainable agriculture projects{target=blank}
Next steps
- You can install Knative Eventing by using the methods listed on the installation page.