Deploy the Knative Eventing add-on to enable event-driven capabilities - Container Service for Kubernetes

Knative Eventing provides a complete event model that lets you ingest events from external systems, such as RocketMQ, Kafka, and Container Registry (ACR), and route them to the appropriate Knative services or functions for processing. Deploy the Knative Eventing add-on in the console to enable event-driven capabilities.

Prerequisites

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

Procedure

Log on to the ACK console. In the left navigation pane, click Clusters.
On the Clusters page, click the name of your cluster. In the left navigation pane, click Applications > Knative.
On the Add-ons tab, find Eventing in the Core Components section. In the Actions column, click Deployments.
If, after you click Deployments, a dialog box appears with the message PrivateZone is not enabled for the current cluster. See Enable PrivateZone when deploying Eventing, complete the following steps to enable PrivateZone.
1. Run the following command to edit the eci-profile file.
```
kubectl -n kube-system edit configmap eci-profile
```
2. Set the enablePrivateZone parameter to true, then save and exit the eci-profile file.
```
apiVersion: v1
data:
  #...
  enablePrivateZone: "true" # Change the parameter value from false to true.
  #...
kind: ConfigMap
metadata:
  name: eci-profile
  namespace: kube-system
```
In the Deploy Eventing dialog box, click OK.
After the deployment is complete, the Add-ons tab shows the status of the Eventing add-on as Deployed.

References

To get started with event-driven architecture, see Send your first event with Knative Eventing.
To implement event-driven architecture based on EventBridge, see Trigger Knative services with EventBridge.