Container Compute Service:Use the event-driven capabilities of EventBridge in Knative

Use the ACS console

1. Log on to the ACS console. In the left-side navigation pane, click Clusters.

2. On the Clusters page, click the ID of the target cluster. In the left-side navigation pane, choose Applications > Knative.

3. Click the Services tab, then click Create from Template.

4. Paste the following YAML and submit:

   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
     name: event-display
     namespace: default
   spec:
     template:
       spec:
         containers:
         - image: registry.cn-hangzhou.aliyuncs.com/knative-sample/event-display:20230207194118_3874dbd

Result: When Created appears in the Status column for event-display on the Services tab, the Knative service is ready.

Use kubectl

1. Create event-display.yaml with the following content:

   apiVersion: serving.knative.dev/v1
   kind: Service
   metadata:
     name: event-display
     namespace: default
   spec:
     template:
       spec:
         containers:
         - image: registry.cn-hangzhou.aliyuncs.com/knative-sample/event-display:20230207194118_3874dbd

2. Apply the manifest:

   kubectl apply -f event-display.yaml

3. Verify the Knative service is ready:

   kubectl get ksvc

   Expected output:

   NAME            URL                                        LATESTCREATED         LATESTREADY           READY   REASON
   event-display   http://event-display.default.example.com   event-display-00001   event-display-00001   True

   READY: True confirms the Knative service is running.

Use the ACS console

1. On the Knative page, click the Services tab, then click the name of the Knative service. On the details page, click the Trigger tab.

2. Click Create Trigger. On the Configure page, set the following parameters:

   Parameter	Description	Example
   Name	Name for the trigger	my-service-trigger
   Broker	Select EventBridge or Other	EventBridge
   Event Source	The source service that emits events	OSS
   Event Type	The event type to filter on; separate multiple types with commas	oss:ActionTrail:ConsoleOperation

Result: After the trigger is created, it appears on the Triggers tab.

Use kubectl

1. Create my-service-trigger.yaml with the following content:

   Field	Description
   broker	Set to eventbridge-default-broker, which maps to the default event bus
   source	The event source supported by EventBridge (for example, acs.oss)
   type	The event type from that source; separate multiple types with commas
   subscriber	The Knative service that receives matching events

   apiVersion: eventing.knative.dev/v1
   kind: Trigger
   metadata:
     name: my-service-trigger
   spec:
     broker: eventbridge-default-broker
     filter:
       attributes:
         source: acs.oss
         type: 'oss:ActionTrail:ConsoleOperation'
     subscriber:
       ref:
         apiVersion: serving.knative.dev/v1
         kind: Service
         name: helloworld-go
         namespace: default

   Key fields:

2. Apply the manifest:

   kubectl apply -f my-service-trigger.yaml

3. Verify the trigger is ready:

   kubectl get triggers

   Expected output:

   NAME                         BROKER                       SUBSCRIBER_URI                                   AGE   READY   REASON
   my-service-trigger           eventbridge-default-broker   http://helloworld-go.default.svc.cluster.local   42h   True

   READY: True confirms the trigger is active and listening for events.