Skip to content

Commit

Permalink
Add Ceph Source to Event Sources
Browse files Browse the repository at this point in the history
Signed-off-by: Zuhair AlSader <[email protected]>
  • Loading branch information
zalsader committed Mar 6, 2024
1 parent 29695ed commit ac66a8e
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions docs/eventing/sources/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,6 +33,7 @@ All Sources are part of the `sources` category.
| [Apache CouchDB](https://github.com/knative-extensions/eventing-couchdb/blob/main/source) | Alpha | Knative | Brings [Apache CouchDB](https://couchdb.apache.org/) messages into Knative. |
| [Apache Kafka](kafka-source/README.md) | Stable | Knative | Brings [Apache Kafka](https://kafka.apache.org/) messages into Knative. The KafkaSource reads events from an Apache Kafka Cluster, and passes these events to a sink so that they can be consumed. See the [Kafka Source](https://github.com/knative-extensions/eventing-kafka/blob/main/pkg/source) example for more details. |
| [ContainerSource](../custom-event-source/containersource/README.md) | Stable | Knative | The ContainerSource instantiates container image(s) that can generate events until the ContainerSource is deleted. This may be used, for example, to poll an FTP server for new files or generate events at a set time interval. Given a `spec.template` with at least a container image specified, the ContainerSource keeps a Pod running with the specified image(s). `K_SINK` (destination address) and `KE_CE_OVERRIDES` (JSON CloudEvents attributes) environment variables are injected into the running image(s). It is used by multiple other Sources as underlying infrastructure. Refer to the [Container Source](../custom-event-source/containersource/README.md) example for more details. |
| [CephSource](https://github.com/knative-extensions/eventing-ceph) | Beta | Knative | The Ceph source converts bucket notifications from [Ceph format](https://docs.ceph.com/docs/master/radosgw/notifications/#events) into CloudEvents format, and inject them into Knative. Conversion logic follow the one described for [AWS S3](https://github.com/cloudevents/spec/blob/master/adapters/aws-s3.md) bucket notifications. |
| [GitHub](https://github.com/knative/docs/tree/main/code-samples/eventing/github-source) | Beta | Knative | Registers for events of the specified types on the specified GitHub organization or repository, and brings those events into Knative. The GitHubSource fires a new event for selected [GitHub event types](https://developer.github.com/v3/activity/events/types/). See the [GitHub Source](https://github.com/knative/docs/tree/main/code-samples/eventing/github-source) example for more details. |
| [GitLab](https://github.com/knative/docs/tree/main/code-samples/eventing/gitlab-source) | Beta | Knative | Registers for events of the specified types on the specified GitLab repository, and brings those events into Knative. The GitLabSource creates a webhooks for specified [event types](https://docs.gitlab.com/ee/user/project/integrations/webhooks.html#events), listens for incoming events, and passes them to a consumer. See the [GitLab Source](https://github.com/knative/docs/tree/main/code-samples/eventing/gitlab-source) example for more details. |
| [KogitoSource](https://github.com/knative-extensions/eventing-kogito) | Alpha | Knative | An implementation of the [Kogito Runtime](https://docs.jboss.org/kogito/release/latest/html_single/#proc-kogito-deploying-on-kubernetes_kogito-deploying-on-openshift) custom resource managed by the [Kogito Operator](https://github.com/kiegroup/kogito-operator). |
Expand Down

0 comments on commit ac66a8e

Please sign in to comment.