Enterprise Distributed Application Service (EDAS) fully integrates Container Service for Kubernetes on the basis of cloud-native Kubernetes. EDAS supports full lifecycle management of Kubernetes containerized applications. A Container Service Kubernetes cluster integrates capabilities of Alibaba Cloud in virtual machines, storage, networking, and security, and provides an excellent runtime environment for Kubernetes containerized applications. This topic describes how to use custom images to deploy applications in a Container Service Kubernetes cluster.
Prerequisites
- Both EDAS and Container Service for Kubernetes are activated for your Alibaba Cloud account. For more information, see the following topics:
- A namespace is created. For more information, see Namespace management.
- Role authorization is complete in Container Service for Kubernetes. For more information, see ACK default roles.
Step 1: Create a Container Service Kubernetes cluster
Log on to the Container Service for Kubernetes console and create a Container Service Kubernetes cluster. For more information, see Create a managed Kubernetes cluster.
To create a Serverless Kubernetes cluster, set VPC to Create VPC and set Service Discovery to PrivateZone. This allows the Serverless Kubernetes cluster to use Alibaba Cloud Service Mesh after the cluster is imported to EDAS. If you set VPC to Select Existing VPC, check whether the cluster contains the virtual private cloud (VPC) and vSwitch resources after you create the cluster.

Step 2: Import the Container Service Kubernetes cluster to the EDAS console
By default, the ack-ahas-sentinel-pilot, ack-arms-pilot, and ack-arms-prometheus components are installed when you add a Kubernetes 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: Create an application in the Container Service Kubernetes cluster
What to do next
After the application is created, you can add an Internet-facing Server Load Balancer (SLB) instance to it for Internet access. You can also add an internal-facing SLB instance so that all nodes in the same VPC can access your application by using this internal-facing SLB instance. For more information, see Bind SLB instances or Reuse an SLB instance.