All Products
Search

This Product

    Enterprise Distributed Application Service:Convert a Deployment to an EDAS application in the EDAS console

    Document Center

    Enterprise Distributed Application Service:Convert a Deployment to an EDAS application in the EDAS console

    Last Updated:Jul 20, 2023

    After a Deployment is created in a Container Service for Kubernetes (ACK) cluster or a hybrid cloud cluster, you can use Enterprise Distributed Application Service (EDAS) to manage the Deployment. This way, you do not need to maintain the Deployment in the cluster. EDAS provides multiple features, such as application lifecycle management, monitoring, and O&M, to help you reduce O&M costs. This topic describes how to convert a Deployment to an EDAS application so that you can manage the Deployment in EDAS.

    Prerequisites

    Background information

    To manage a Deployment in EDAS, you must 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 to an EDAS application with a few clicks.

    Note

    In EDAS, the procedure of managing ACK clusters is similar to that of managing hybrid cloud clusters. In this topic, an ACK cluster is used to describe the procedure.

    Import an ACK cluster to 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) component. The ack-arms-prometheus component is a Prometheus monitoring component.

    1. Log on to the EDAS console. In the left-side navigation pane, choose Resource Management > Container Service Kubernetes Clusters.

    2. In the top navigation bar, select the region in which your ACK cluster resides, and click Synchronize Container Service Kubernetes Cluster.

    3. Find the ACK cluster that is synchronized to EDAS and click Import in the Actions column.

    4. In the Precheck for Import dialog box, click Continue.

    5. In the Import Kubernetes Cluster dialog box, select the microservice namespace to which you want to import the ACK cluster from the Microservice Namespace drop-down list, turn on or off Service Mesh based on your business requirements, and then click Import.

      If the value in the Cluster Status column is Running and the value in the Import Status column is Imported for the ACK cluster, the cluster is imported to EDAS.

    Convert a Deployment to an EDAS application in the EDAS console

    1. Log on to the EDAS console. In the left-side navigation pane, choose Resource Management > Container Service Kubernetes Clusters.

    2. In the top navigation bar of the Container Service Kubernetes Cluster page, select a region. Then, select a microservices namespace from the Microservice Namespace drop-down list.

    3. On the Container Service Kubernetes Cluster page, click the ID of the cluster that you want to manage.

    4. In the Deployments section of the Cluster Details page, find the Deployment that you want to convert and click Convert in the Actions column.

    5. In the Convert Application dialog box, click OK.

      Note

      After you convert a Deployment, the Deployment is restarted. Do not perform this operation during peak hours.

      After the conversion task is complete, the status of the Deployment becomes Converted, and the converted application appears in the Applications section.

      Note

      If you no longer need to use EDAS to manage your Deployment, you can cancel the conversion. After you cancel the conversion, the converted application is deleted from EDAS.

    Related topics

    After a Deployment 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 or continuous deployment (CI/CD), monitor the application, and perform O&M operations.