Deploy Knative Eventing to enable event-driven capability - Container Service for Kubernetes

Knative Eventing provides an event model, which can be used to interface with external event systems, such as GitHub, ApsaraMQ for RocketMQ, ApsaraMQ for Kafka, and Container Registry, and route events to Knative Services or Functions for processing. You can deploy Knative Eventing through the console to enable the event-driven capability.

Prerequisites

Knative has been deployed in your cluster. For more information, see Deploy Knative.

Procedure

Log on to the ACK console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to manage and click its name. In the left-side navigation pane, choose Applications > Knative.
In the Core Component section of the Components tab, click Deploy in the Actions column of Eventing.
After you click Deploy, if the PrivateZone is not enabled for the cluster. For more information, see Enable PrivateZone when you deploy Knative Eventing error appears in the Deploy Eventing dialog box, you must perform the following steps to enable Alibaba Cloud DNS PrivateZone.
1. Run the following command to modify the eci-profile file:
```
kubectl -n kube-system edit configmap eci-profile
```
2. Set enablePrivateZone to true. Save and close the eci-profile file.
```
apiVersion: v1
data:
  #...
  enablePrivateZone: "true" # Change the value from false to true. 
  #...
kind: ConfigMap
metadata:
  name: eci-profile
  namespace: kube-system
```
In the Deploy Eventing dialog box, click Confirm.
After Knative Eventing is deployed, the component is in the Deployed state on the Components tab.

References

You can use Knative Eventing to interface with different event sources. For more information, see Use Knative to manage GitHub events, Use Knative to manage MnsOss event sources, and Use EventBridge to trigger Knative Services to consume events.