Knative is an open source Kubernetes-based serverless framework. Knative supports pod auto scaling based on resource requests, version management, and canary releases for applications. When no traffic is processed, the number of pods is scaled to zero. ACS Knative is completely compatible with open source Knative and allows you to deploy Services with a few clicks. It saves you the need to purchase resources. You can use the ACS console to deploy ACS Knative and then enable Knative Ingresses.
Prerequisites
An ACS cluster is created. For more information, see Create an ACS cluster.
Procedure
Log on to the ACS console. In the left-side navigation pane, click Clusters.
On the Clusters page, find the cluster that you want to manage and click its ID. In the left-side navigation pane of the cluster details page, choose .
On the Components tab, click Deploy Knative, select the Knative Ingress that you want to install, and then click Deploy.
For suggestions on selecting Knative Ingresses, see Suggestions on selecting Knative Ingresses.
ALB
ALB Ingresses are fully managed and provide a more efficient method to manage ingress traffic based on ALB. ALB Ingresses support complex routing, automatic certificate discovery, and the HTTP, HTTPS, and QUIC protocols.
NoteIf you use ALB Ingresses, you must select at least two vSwitches. For more information about the regions in which ALB is available, see Regions and zones in which ALB is available.
MSE
MSE Ingresses are developed based on MSE cloud-native gateways and provide a more efficient method to manage ingress traffic. MSE Ingresses are compatible with NGINX Ingresses and more than 50 annotations defined in NGINX Ingresses. MSE Ingresses are suitable for more than 90% of scenarios supported by NGINX Ingresses. MSE Ingresses allow you to roll out multiple canary versions at the same time, and provide flexible service governance capabilities and comprehensive protection. MSE Ingresses can meet the requirements for traffic governance in scenarios in which a large number of cloud-native distributed applications are used.
ASM
Alibaba Cloud Service Mesh (ASM) is a fully managed service mesh platform. ASM is compatible with the open source Istio service mesh. ASM simplifies service management. For example, you can use ASM to route and split inter-service traffic, secure inter-service communication based on authentication, and observe the behavior of services in meshes. This greatly reduces your development and O&M work.
Kourier
Kourier Ingresses are provided by the Knative community and provide basic routing capabilities. Kourier Ingresses are deployed in your clusters and must be manually maintained.
After the components are deployed, you can click Go to Components to view details about the components or click Go to Services to view details about the Knative Services.
What to do next
Deploy components: On the Components tab, find a component whose Status column displays Not Deployed and click Deploy in the Actions column. In the message that appears, click Confirm.
Uninstall components: On the Components tab, find the component that you want to uninstall and click Uninstall in the Actions column. In the message that appears, click Confirm.
Uninstall Knative: On the Components tab, click Uninstall in the upper right corner. In the dialog box that appears, select I confirm that I have read the above information and want to uninstall Knative and click OK.
References
For more information about how to select Knative Ingresses, see Suggestions on selecting Knative Ingresses.
You can refer to Quickly deploy a Knative Service to deploy a Knative Service.
For more information about how to implement auto scaling for a Knative Service based on requests, see Configure auto scaling based on the number of requests.
For more information about how to deploy Knative Eventing and implement Knative event-driven scaling, see Knative Eventing.