Assume that a Deployment application is created in a Kubernetes cluster that is deployed on Alibaba Cloud or a third-party cloud or in a self-managed Kubernetes cluster deployed in data centers. You do not need to host the application in the cluster. Instead, you can use EDAS to host the application. EDAS provides multiple features, such as application lifecycle management, monitoring, and O&M. These features can help you reduce your O&M costs in a significant way. This topic describes how to convert a Deployment application to an application in EDAS.

Background information

Before you use EDAS to host the Deployment application, create or register a cluster in the Container Service for Kubernetes (ACK) console, import the cluster to the EDAS console, and then convert the Deployment application in the imported cluster within a few clicks.

Note In EDAS, the procedure of managing Kubernetes clusters that are deployed on Alibaba Cloud is similar to that of managing Kubernetes clusters that are deployed in a third-party cloud or self-managed Kubernetes clusters deployed in data centers. In this topic, the procedure of managing a Container Service Kubernetes cluster is used as an example.

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.

  1. Log on to the EDAS console.
  2. In the left-side navigation pane, choose Resource Management > Container Service Kubernetes Clusters.
  3. In the top navigation bar, select the region where you want to import the cluster, and click Synchronize Container Service Kubernetes Cluster.
  4. In the Actions column of the Container Service Kubernetes cluster that you want to import, click Import.
  5. In the Import Kubernetes Cluster dialog box, select the destination namespace from the Namespace drop-down list, turn on or off Service Mesh, and then click Import.
    If the value of Cluster Status is Running and the value of Import Status is Imported. for the Container Service Kubernetes cluster, the Container Service Kubernetes cluster is imported to EDAS.

Convert a Deployment application to an application in EDAS

  1. Log on to the EDAS console.
  2. In the left-side navigation pane, choose Resource Management > Container Service Kubernetes Clusters.
  3. In the top navigation bar of the Container Service Kubernetes Cluster page, select a region. Then, select a namespace.
  4. On the Container Service Kubernetes Cluster page, click the ID of the cluster that you want to manage.
  5. In the Deployments section of the cluster details page, click Convert in the Actions column.
  6. In the Convert Application dialog box, click OK.
    Note After you convert an application, the application is restarted. Do not perform this operation during peak hours.
    After the conversion task is completed, the status of the Deployment application becomes Converted, and the converted application appears on the Applications page.
    Note If you no longer need EDAS to host your Deployment application, you can cancel the conversion. After you cancel the conversion, this application is deleted from EDAS.

Subsequent operations

After the application is converted, you can perform all the operations that you can perform on applications that are deployed by using JAR packages, WAR packages, and images. For example, you can upgrade and roll back the application, perform continuous integration and continuous deployment, monitor the application, and perform O&M operations.