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.

Procedure of deploying an application in a Kubernetes cluster

Prerequisites

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.

  1. Log on to the EDAS console.
  2. In the left-side navigation pane, choose Resource Management > Serverless Kubernetes Clusters.
  3. In the top navigation bar, select the region of the microservice namespace that you want to manage. From the Microservice Namespace drop-down list, select the namespace to which you want to import the serverless Kubernetes cluster. Then, click Synchronize Serverless Kubernetes Cluster.
  4. Find the serverless Kubernetes cluster to be imported and click Import in the Actions column.
    If the serverless Kubernetes cluster is in the Running state and the value in the Import Status column of the serverless Kubernetes cluster is Imported, the serverless Kubernetes cluster is imported to EDAS as expected.

Step 3: Deploy an application in the serverless Kubernetes cluster

Note The procedure of deploying an application by using a WAR package is the same as that by using a JAR package. The example in this topic shows you how to use a JAR package to deploy an application.
  1. Log on to the EDAS console.
  2. In the left-side navigation pane, click Applications. In the top navigation bar, select a region. In the upper part of the page, select a namespace. In the upper-left corner of the Applications page, click Create Application.
  3. In the Basic Information step, set the parameters in the Cluster Type and Application Runtime Environment sections and click Next.
    Configure basic information
    Section Description
    Cluster Type The type of the cluster in which you want to deploy the application. Select Kubernetes Clusters.
    Application Runtime Environment
    Hosted Applications The programming language in which the application is developed. In this example, select Java. For information about how to deploy a PHP application or a multilingual application, see Build PHP applications from source code and deploy them in ACK clusters and Deploy a microservice-based multi-language application.
    Select Application The runtime environment of the application. This topic describes how to use a JAR or WAR package to deploy a Java application. In actual scenarios, select an option based on your needs. Valid values: Java, Tomcat, and EDAS-Container (HSF). For information about how to deploy an application by using an image, see Use an image to deploy an application in a.
    • Java: Select this option if you want to use a universal JAR package to deploy the application as a Dubbo or a Spring Boot application. You can set the Java Environment parameter after you select this option.
    • Tomcat: Select this option if you want to use a universal WAR package to deploy the application as a Dubbo or a Spring application. You can set the Java Environment and Container Version parameters after you select this option.
    • EDAS-Container (HSF): Select this option if you want to use a WAR or FatJar package to deploy the application as a High-Speed Service Framework (HSF) application. You can set the Java Environment, Pandora Version, and Ali-Tomcat Version parameters after you select this option.
    Service Registration and Discovery The O&M method for your service registry. For more information, see Select an O&M method for your service registry.
  4. In the Configurations step, configure the environment information, basic information, and deployment method for the application, set the related resource parameters, and then click Next.
    Application configuration - use a JAR package to deploy an application in the Kubernetes cluster
    Parameter Description
    Microservice Namespace The microservice namespace of the serverless Kubernetes cluster. If you have not created a microservice namespace or do not select a microservice namespace, this parameter is set to Default.

    If you have not created a microservice namespace or you want to create another microservice namespace, click Create Microservice Namespace to create a microservice namespace. For more information, see the "Create a namespace" section of the Manage microservice namespaces topic.

    Cluster The cluster in which you want to deploy the application. From the Cluster drop-down list, select the imported serverless Kubernetes cluster.

    If the selected Kubernetes cluster is not imported to EDAS, select This cluster is used for the first time in EDAS. If you select this check box, the cluster is imported to EDAS when an application is created. This consumes a certain amount of time. Then, check whether Alibaba Cloud Service Mesh is activated.

    Note You can select a cluster that is not in the microservice namespace in which you want to deploy the application.
    K8s Namespace The Kubernetes namespace of the cluster. Internal system objects are allocated to different Kubernetes namespaces to form logically isolated projects, groups, or user groups. This way, these projects, groups, or user groups can be separately managed but still share the resources of the entire cluster. Valid values:
    • default: the default Kubernetes namespace. If no Kubernetes namespace is specified for an object, the default Kubernetes namespace is used.
    • kube-system: the Kubernetes namespace of the objects that are created by the system.
    • kube-public: the Kubernetes namespace that is automatically created and can be read by all users, including users who are not authenticated.

    In this example, default is selected.

    If you want to create a custom Kubernetes namespace, click Create Kubernetes Namespace. In the dialog box that appears, enter a name for the Kubernetes namespace in the K8s Namespace field. The name can contain digits, lowercase letters, and hyphens (-), and can be 1 to 63 characters in length. It must start and end with a letter or a digit.

    Application Name The name of the application. The name must start with a letter and can contain digits, letters, and hyphens (-). The application name can be up to 36 characters in length.
    Application Description The description of the application. The description can be up to 128 characters in length.
    Source of Deployment Package
    • Custom Program
      If you select this option, the File Uploading Method parameter is required. Valid values of the File Uploading Method parameter:
      • Upload JAR Package: Select and upload the JAR package that you have downloaded.
      • JAR Package Address: Enter the address of the demo package.
    • Official Demo

      EDAS provides the following demo types: Spring Cloud Server Application, Spring Cloud Application, Dubbo Server Application, and Dubbo Application. Select a demo type based on your needs.

    Version The version of the application. You can specify a custom version number or click Use Timestamp as Version Number to generate a version number.
    Time Zone The time zone for the application.
    Total Pods The number of pods on which the application is to be deployed.
    Single-pod Resource Quota The amount of CPU and memory resources that you want to reserve for a pod. To set a limit, enter a numeric value. The default value 0 indicates that no limit is set.
  5. Optional. In the Advanced Settings step, configure the advanced settings.
  6. Click Create Application.
    The application requires several minutes to be deployed. During the process, you can view the change records to track the deployment progress of the application. For more information, see View the overall information about an application. After the application is deployed, the Application Overview page appears. On this page, you can check the status of the pod. If the pod is in the Running state, the application is released. You can click the state of the pod to view the advanced settings of the application instance, such as Deployment, Pod, and Startup Command.

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.