Skip to content

Commit

Permalink
Introduce ClusterCloudEventSource (#1398)
Browse files Browse the repository at this point in the history
  • Loading branch information
SpiritZhou authored Nov 7, 2024
1 parent 9f7c604 commit f565629
Showing 1 changed file with 14 additions and 0 deletions.
14 changes: 14 additions & 0 deletions content/docs/2.15/operate/cloud-events.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,21 @@ In general, an event emitted by KEDA would fundamentally come down to the follow
}
}
```
### Scopes: Namespace vs. Cluster

Each `CloudEventSource` is defined in one namespace and will only subscribe to events inside that namespace. If you want to subscribe to events in all namespaces, you can instead create a `ClusterCloudEventSource` resource.

Defining a `ClusterCloudEventSource` works almost identically to a `CloudEventSource`, except there is no `metadata.namespace` value:

```yaml
apiVersion: keda.sh/v1alpha1
kind: ClusterCloudEventSource
metadata:
name: {cluster-cloudeventsource-name}
spec:
# As before ..
```

## Event Sinks

There will be multiple types of destination to emit KEDA events to.
Expand Down

0 comments on commit f565629

Please sign in to comment.