Skip to content

Commit

Permalink
Update
Browse files Browse the repository at this point in the history
Signed-off-by: SpiritZhou <iammrzhouzhenghan@gmail.com>
  • Loading branch information
SpiritZhou committed May 28, 2024
1 parent 6f03d81 commit a4f13c0
Showing 1 changed file with 15 additions and 0 deletions.
15 changes: 15 additions & 0 deletions content/docs/2.15/operate/events.md
Original file line number Diff line number Diff line change
Expand Up @@ -79,6 +79,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. For cases where you want to share a single sink among many namespaces, you can instead create a `ClusterCloudEventSource`. As a global object, this can be used from any namespace.

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 a4f13c0

Please sign in to comment.