Knative Eventing provides an event model for routing events from external systems—such as ApsaraMQ for RocketMQ, ApsaraMQ for Kafka, and Container Registry—to Knative Services or Functions. Deploy it through the ACK console to enable event-driven workloads in your cluster.
Prerequisites
Before you begin, ensure that you have:
Knative deployed in your cluster. For more information, see Deploy Knative.
Deploy Knative Eventing
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, choose Applications > Knative.
On the Components tab, find Eventing in the Core Component section and click Deploy in the Actions column.
In the Deploy Eventing dialog box, click Confirm.
After deployment, the Eventing component shows a Deployed status on the Components tab.
Troubleshooting
PrivateZone is not enabled for the cluster
If the Deploy Eventing dialog box shows the error "PrivateZone is not enabled for the cluster. For more information, see Enable PrivateZone when you deploy Knative Eventing," enable Alibaba Cloud DNS PrivateZone before deploying:
Run the following command to open the
eci-profileConfigMap for editing:kubectl -n kube-system edit configmap eci-profileSet
enablePrivateZoneto"true", then save and close the file:apiVersion: v1 data: #... enablePrivateZone: "true" # Change the value from false to true. #... kind: ConfigMap metadata: name: eci-profile namespace: kube-systemReturn to step 3 of the deployment procedure and click Deploy again.