subscriptions.eventing.kyma-project.io CustomResourceDefinition (CRD) is a detailed description of the kind of data and the format used to subscribe to events. To get the up-to-date CRD and show the output in the YAML format, run this command:
kubectl get crd subscriptions.eventing.kyma-project.io -o yaml
Sample custom resource
This sample Subscription custom resource (CR) subscribes to an event called
WARNING: Prohibited characters in event names under the spec.types property, are not supported in some backends. If any are detected, Eventing will remove them. Read Event names for more information.
NOTE: Both the subscriber and the Subscription should exist in the same Namespace.
apiVersion: eventing.kyma-project.io/v1alpha2kind: Subscriptionmetadata:name: testnamespace: testspec:typeMatching: standardsource: commercetypes:- order.created.v1sink: http://test.test.svc.cluster.localconfig:maxInFlightMessages: "10"
Custom resource parameters
This table lists all the possible parameters of a given resource together with their descriptions:
|metadata.name||Yes||Specifies the name of the CR.|
|metadata.namespace||No||Defines the Namespace in which the CR is available. It is set to |
|spec.typeMatching||No||Defines the matching type (|
|spec.source||Yes||The origin from which events are published.|
|spec.types||Yes||Defines the list of event types used to trigger workloads.|
|spec.sink||Yes||Specifies the HTTP endpoint where matching events should be sent to, for example: |
|spec.config.maxInFlightMessages||No||The maximum idle "in-flight messages" sent by NATS to the sink without waiting for a response. By default, it is set to 10.|
Related resources and components
These components use this CR:
|Eventing Controller||The Eventing Controller reconciles on Subscriptions and creates a connection between subscribers and the Eventing backend.|
|Event Publisher Proxy||The Event Publisher Proxy reads the Subscriptions to find out how events are used for each Application.|