Enterprise Distributed Application Service (EDAS) integrates with Container Service for Kubernetes (ACK) on the basis of cloud-native Kubernetes. EDAS allows you to manage the full lifecycle of Kubernetes containerized applications. Serverless Kubernetes clusters are applicable to agile business scenarios that require fast scaling. This topic describes how to use a demo JAR package or a demo WAR package provided by EDAS to deploy an application in a serverless Kubernetes cluster.
Background information
To deploy an application in a serverless Kubernetes cluster, create a serverless Kubernetes in the ACK console. Then, import the cluster in the EDAS console, and use a deployment package or an image to deploy the application in the imported cluster.

Prerequisites
- Both EDAS and ACK are activated for your Alibaba Cloud account. For more information, see the following topics:
- A microservice namespace is created. For more information, see the "Create a microservice namespace" section of the Manage microservice namespaces in the EDAS console topic.
- Role authorization is complete in ACK. For more information, see ACK default roles.
Step 1: Create a serverless Kubernetes cluster
Log on to the ACK console and create a serverless Kubernetes cluster. For more information, see Create an ASK cluster.
Step 2: Import the serverless Kubernetes cluster in the EDAS console
By default, the ack-ahas-sentinel-pilot, ack-arms-pilot, and ack-arms-prometheus components are installed when you import an ACK cluster to EDAS in the EDAS console. The ack-ahas-sentinel-pilot component is an application protection component for throttling and degradation. The ack-arms-pilot component is an Application Real-Time Monitoring Service (ARMS) monitoring component. The ack-arms-prometheus component is a Prometheus monitoring component.
Step 3: Deploy an application in the serverless Kubernetes cluster
What to do next
After the application is deployed, you can add an Internet-facing Server Load Balancer (SLB) instance to allow access to the application over the Internet. You can also add an internal-facing SLB instance so that all the nodes in the same VPC can access the application by using this internal-facing SLB instance. For more information, see Add an SLB instance to an application in a Kubernetes cluster.
DingTalk group for Container Service for Kubernetes and Serverless Kubernetes clusters in EDAS
If you have questions or suggestions when you use Container Service for Kubernetes
and Serverless Kubernetes clusters in EDAS, submit a ticket. To give feedback, you can also join the DingTalk group by searching for the DingTalk
group ID 23197114
.